| 2.1 | Approval of the agenda | |
|---|---|---|
| R2-2102600 | Agenda for RAN2#113bis-e | Chairman |
| 2.2 | Approval of the report of the previous meeting | |
| R2-2102601 | RAN2#113-e Meeting Report | MCC |
| 2.4 | Others | |
| R2-2104359 | Reserved for breakout session | MCC |
| R2-2104378 | Reserved for breakout session | MCC |
| R2-2104379 | Reserved for breakout session | MCC |
| R2-2104380 | Reserved for breakout session | MCC |
| R2-2104381 | Reserved for breakout session | MCC |
| R2-2104382 | Reserved for breakout session | MCC |
| R2-2104383 | Reserved for breakout session | MCC |
| R2-2104384 | Reserved for breakout session | MCC |
| R2-2104393 | Reserved for breakout session | MCC |
| R2-2104394 | Reserved for breakout session | MCC |
| R2-2104403 | Reserved for breakout session | MCC |
| R2-2104404 | Reserved for breakout session | MCC |
| R2-2104416 | Reserved for breakout session | MCC |
| R2-2104419 | Reserved for breakout session | MCC |
| R2-2104421 | Reserved for breakout session | MCC |
| R2-2104422 | Reserved for breakout session | MCC |
| R2-2104423 | Reserved for breakout session | MCC |
| R2-2104424 | Reserved for breakout session | MCC |
| R2-2104425 | Reserved for breakout session | MCC |
| R2-2104426 | Reserved for breakout session | MCC |
| R2-2104427 | Reserved for breakout session | MCC |
| R2-2104428 | Reserved for breakout session | MCC |
| R2-2104429 | Reserved for breakout session | MCC |
| R2-2104432 | Reserved for breakout session | MCC |
| R2-2104437 | Reserved for breakout session | MCC |
| R2-2104440 | Reserved for breakout session | MCC |
| R2-2104443 | Reserved for breakout session | MCC |
| R2-2104445 | Reserved for breakout session | MCC |
| R2-2104446 | Reserved for breakout session | MCC |
| R2-2104447 | Reserved for breakout session | MCC |
| R2-2104448 | Reserved for breakout session | MCC |
| R2-2104449 | Reserved for breakout session | MCC |
| R2-2104452 | Reserved for breakout session | MCC |
| R2-2104453 | Reserved for breakout session | MCC |
| R2-2104454 | Reserved for breakout session | MCC |
| R2-2104455 | Reserved for breakout session | MCC |
| R2-2104456 | Reserved for breakout session | MCC |
| R2-2104457 | Reserved for breakout session | MCC |
| R2-2104458 | Reserved for breakout session | MCC |
| R2-2104459 | Reserved for breakout session | MCC |
| R2-2104476 | Reserved for breakout session | MCC |
| R2-2104477 | Reserved for breakout session | MCC |
| R2-2104478 | Reserved for breakout session | MCC |
| R2-2104479 | Reserved for breakout session | MCC |
| R2-2104480 | Reserved for breakout session | MCC |
| R2-2104481 | Reserved for breakout session | MCC |
| R2-2104482 | Reserved for breakout session | MCC |
| R2-2104483 | Reserved for breakout session | MCC |
| R2-2104484 | Reserved for breakout session | MCC |
| R2-2104485 | Reserved for breakout session | MCC |
| R2-2104486 | Reserved for breakout session | MCC |
| R2-2104487 | Reserved for breakout session | MCC |
| R2-2104488 | Reserved for breakout session | MCC |
| R2-2104489 | Reserved for breakout session | MCC |
| 3 | Incoming liaisons | |
| R2-2102603 | LS on broadcasting from other PLMN in case of Disaster Condition (C1-211189; contact: LGE) | CT1 |
| R2-2102606 | LS on Information on the port number allocation solutions (C4-211806; contact: Huawei) | CT4 |
| 4.4 | Positioning corrections Rel-15 and earlier | |
| R2-2102916 | Corrections on the field description of commonIEsProvideAssistanceData in TS36.355 | CATT, Huawei, HiSilicon |
| R2-2102917 | Corrections on the acquisition of a posSI message | CATT |
| R2-2102918 | Corrections on the acquisition of a posSI message | CATT |
| R2-2103216 | Correction on SUPL support of positioning methods | Samsung |
| R2-2103217 | Correction on SUPL support of positioning methods | Samsung |
| R2-2103218 | Correction on SUPL support of positioning methods | Samsung |
| R2-2103603 | Correction to need code for DL LPP message-R16 | Huawei, HiSilicon |
| R2-2103604 | Correction to need code for DL LPP message-R15 | Huawei, HiSilicon |
| R2-2103605 | Correction to need code for DL LPP message-R14 | Huawei, HiSilicon |
| R2-2103606 | Correction to need code for DL LPP message-R13 | Huawei, HiSilicon |
| R2-2103607 | Correction to need code for DL LPP message-R12 | Huawei, HiSilicon |
| R2-2103608 | Correction to need code for DL LPP message-R11 | Huawei, HiSilicon |
| R2-2103609 | Correction to need code for DL LPP message-R10 | Huawei, HiSilicon |
| R2-2103610 | Correction to need code for DL LPP message-R9 | Huawei, HiSilicon |
| R2-2103616 | Correction to need code for DL LPP message-R16 | Huawei, HiSilicon |
| R2-2104517 | Summary of [AT113bis-e][601][POS] Positioning Corrections for R-15 and earlier | Huawei, HiSilicon |
| R2-2104518 | Corrections on the acquisition of a posSI message | CATT |
| R2-2104519 | Corrections on the acquisition of a posSI message | CATT |
| R2-2104524 | Correction to need code for DL LPP message-R15 | Huawei, HiSilicon, Lenovo |
| R2-2104525 | Correction to need code for DL LPP message-R16 | Huawei, HiSilicon, Lenovo |
| 4.5 | Other LTE corrections Rel-15 and earlier | |
| R2-2103813 | On the lack of PLMN identity check in case of anyCellSelected state related logging | Ericsson |
| R2-2103814 | On the lack of PLMN identity check in case of anyCellSelected state related logging | Ericsson |
| R2-2103816 | On the lack of PLMN identity check in case of anyCellSelected state related logging | Ericsson |
| R2-2104013 | Discussion on one-shot configuration | Huawei, HiSilicon |
| R2-2104014 | Correction on category dependency for DL Category 13 | Huawei, HiSilicon |
| R2-2104248 | Correction on T325 | Google Inc. |
| R2-2104253 | Correction on T325 | Google Inc. |
| R2-2104310 | Summary of [AT113bis-e][201][LTE] LTE Miscellaneous R15/16 corrections (Ericsson) | Ericsson |
| R2-2104323 | Summary of [AT113bis-e][203][LTE] One-shot configurations (Huawei) | Huawei |
| R2-2104341 | Correction on category dependency for DL Category 13 | Huawei, HiSilicon |
| 5.1 | Organisational | |
| R2-2102649 | Second Reply LS to RP-202935 = R4-2100025 on BCS reporting and support for intra-band EN-DC band combinations (R4-2103401; contact: T-Mobile USA) | RAN4 |
| R2-2102654 | LS on BCS reporting and support for intra-band EN-DC band combinations (RP-202935; contact: Nokia) | RAN |
| 5.2.1 | TS 3x.300 | |
| R2-2102674 | LS on Handover terminology (S5-211324; contact: Ericsson) | SA5 |
| R2-2102901 | Clarification on UL data transmission along with RRCReconfigurationComplete during HO | OPPO, Nokia (Rapporteur), CMCC, Xiaomi, Huawei, HiSilicon |
| R2-2102902 | Clarification on UL data transmission along with RRCReconfigurationComplete during HO | OPPO, Nokia (Rapporteur), CMCC, Xiaomi, Huawei, HiSilicon |
| R2-2102941 | Intra and Inter Frequency Scenarios | Nokia (Rapporteur) |
| R2-2102942 | Intra and Inter Frequency Scenarios | Nokia (Rapporteur) |
| R2-2103337 | 38.300 CR: removing ambiguous HO naming | Nokia, Nokia Shanghai Bell |
| R2-2103338 | 36.300 CR: removing ambiguous HO naming | Nokia, Nokia Shanghai Bell |
| R2-2103339 | Response LS to SA5 on handover terminology | Nokia, Nokia Shanghai Bell |
| R2-2103479 | Correction on random access procedure for resume procedure | Nokia (Rapporteur) |
| R2-2103485 | Correction on random access procedure for resume procedure | Nokia (Rapporteur) |
| R2-2103653 | Clarification to data forwarding at full configuration | Ericsson |
| R2-2103654 | Clarification to data forwarding at full configuration | Ericsson |
| R2-2103983 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (rapporteur) |
| R2-2103984 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (rapporteur) |
| R2-2104010 | Discussion on handover terminology based on SA5 LS S5-211324 | Huawei, HiSilicon |
| R2-2104011 | Correction on handover terminology | Huawei, HiSilicon |
| R2-2104012 | Correction on handover terminology | Huawei, HiSilicon |
| R2-2104358 | Response LS to SA5 on handover terminology | RAN2 |
| R2-2104515 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (rapporteur) |
| R2-2104516 | SRB PDCP handling upon handover | Huawei, HiSilicon, Nokia (rapporteur) |
| 5.2.2 | TS 37.340 | |
| R2-2103651 | Clarification to data forwarding upon SN change with full configuration | Ericsson |
| R2-2103652 | Clarification to data forwarding upon SN change with full configuration | Ericsson |
| 5.3.1 | MAC | |
| R2-2102683 | Correction to DRX active time criteria with CSI masking | Qualcomm Incorporated |
| R2-2102684 | Correction to DRX active time criteria with CSI masking | Qualcomm Incorporated |
| R2-2103448 | Correction on Truncated BSR | ASUSTeK |
| R2-2103848 | Error handling of invalid MAC PDU formats | Apple |
| R2-2104053 | Clarification on reporting multiplexed CSI on PUCCH in DRX | Huawei, HiSilicon |
| R2-2104086 | Clarification on SUL switch | LG Electronics UK |
| R2-2104091 | Clarification on DL HARQ process number | Huawei, HiSilicon |
| R2-2104092 | Clarification on DL HARQ process number | Huawei, HiSilicon |
| R2-2104533 | Report of [AT113bis-e][003][NR15] MAC (Samsung) | Samsung |
| 5.3.2 | RLC PDCP SDAP | |
| R2-2103301 | Discussion on the issue of PDCP re-establishment after RRC re-establishment | NEC |
| R2-2103302 | Correction on PDCP re-establishment after RRC re-establishment | NEC |
| R2-2103303 | Correction on PDCP re-establishment after RRC re-establishment | NEC |
| R2-2104201 | Integrity check for interspersed ROHC feedback | LG Electronics Inc. (PDCP rapporteur) |
| R2-2104202 | Integrity check for interspersed ROHC feedback | LG Electronics Inc. (PDCP rapporteur) |
| R2-2104293 | Clarification on the change of PDU session ID | Samsung Electronics Iberia SA |
| R2-2104534 | Report of [AT113bis-e][004][NR15] PDCP SDAP | LG Electronics Inc. (Rapporteur) |
| 5.4.1.1 | Connection control | |
| R2-2102715 | Corrections to initiation upon reception of RAN paging and T380 Expiry | Samsung Electronics Co., Ltd |
| R2-2103535 | Correction on contention resolution timer (R15) | Huawei, HiSilicon |
| R2-2103536 | Correction on contention resolution timer (R16) | Huawei, HiSilicon |
| R2-2103655 | Clarification on SRB1 configuration for RRC resume and reestablishment | Ericsson, Intel Corporation, ZTE Corporation |
| R2-2103656 | Clarification on SRB1 configuration for RRC resume and reestablishment | Ericsson, Intel Corporation, ZTE Corporation |
| R2-2103657 | Clarification on the RLC entity release during full configuration | Ericsson |
| R2-2103658 | Clarification on the RLC entity release during full configuration | Ericsson |
| R2-2103659 | Resume of measurements during the RRC resume procedure | Ericsson |
| R2-2103660 | Resume of measurements during the RRC resume procedure | Ericsson |
| R2-2103746 | Clarification on RRC full config for intra-SN PSCell change | NTT DOCOMO, INC., Ericsson, Fujitsu |
| R2-2103748 | Clarification on RRC full config for intra-SN PSCell change | NTT DOCOMO, INC., Ericsson, Fujitsu |
| R2-2103752 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
| R2-2103753 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
| R2-2103754 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
| R2-2103790 | Discussion on the release of active BWP | ZTE Corporation, Sanechips |
| R2-2103793 | Correction on firstActiveDownlinkBWP-Id | ZTE Corporation, Sanechips |
| R2-2103794 | Correction on firstActiveDownlinkBWP-Id | ZTE Corporation, Sanechips |
| R2-2103859 | NR-DC Clarification | Apple |
| R2-2103860 | Clarification on the RRC Processing Delay | Apple |
| R2-2103861 | Clarification on the RRC Processing Delay | Apple |
| R2-2104077 | Clarification on SCG failure information | ZTE Corporation, Sanechips |
| R2-2104078 | CR on SCG failure information | ZTE Corporation, Sanechips |
| R2-2104079 | CR on SCG failure information | ZTE Corporation, Sanechips |
| R2-2104080 | CR on SCG failure information | ZTE Corporation, Sanechips |
| R2-2104090 | CR on SCG failure information | ZTE Corporation, Sanechips |
| R2-2104093 | Radio bearer handling upon SCG RLF | Huawei, HiSilicon |
| R2-2104094 | Radio bearer handling upon SCG RLF | Huawei, HiSilicon |
| R2-2104095 | Discussion on active BWP release | Huawei, HiSilicon |
| R2-2104127 | Clarification on RLC bearer handling in Full Configuration | MediaTek Inc., Qualcomm Incorporated |
| R2-2104140 | Clarification on RLC bearer handling in full configuration | MediaTek Inc., Qualcomm Incorporated |
| R2-2104143 | Clarification on RLC bearer handling in full Configuration | MediaTek Inc., Qualcomm Incorporated |
| R2-2104254 | Correction on T325 | Google Inc. |
| R2-2104255 | Correction on T325 | Google Inc. |
| R2-2104267 | Clarification on the abortion of RRC connection establishment | Huawei, HiSilicon |
| R2-2104268 | Clarification on the abortion of RRC connection establishment | Huawei, HiSilicon |
| R2-2104300 | Discussion on the release of active BWP | ZTE Corporation, Sanechips |
| R2-2104578 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
| R2-2104579 | Clarification on SCellIndex and ServCellIndex | NTT DOCOMO, INC. |
| R2-2104601 | Correction on T325 | Google Inc. |
| R2-2104602 | Correction on T325 | Google Inc. |
| R2-2104615 | Phase I summary of [AT113bis-e][006][NR15] Conn Control II | Huawei, HiSilicon |
| R2-2104616 | Phase 2 summary of [AT113bis-e][006][NR15] Conn Control II | Huawei, HiSilicon |
| R2-2104633 | Summary [AT113bis-e][005][NR15] Connection Control I | ZTE Corporation (offline discussion rapporteur) |
| 5.4.1.2 | Inter-Node RRC messages | |
| R2-2102768 | Additional aspects on MN SN config restrictions | Nokia, Nokia Shanghai Bell |
| R2-2102769 | Clarification on sCellFrequencies | Nokia, Nokia Shanghai Bell |
| R2-2103027 | Further clarify MN and SN configuration restrictions | ZTE Corporation, Sanechips |
| R2-2103028 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips |
| R2-2103029 | CR on MN and SN configuration restriction coordination | ZTE Corporation, Sanechips |
| R2-2103228 | Clarification on full and delta configuration signalling for inter-MN handover without SN change | Nokia, Nokia Shanghai Bell |
| R2-2103641 | Clean-up of INM procedure text | Ericsson |
| R2-2103642 | Clean-up of INM procedure text | Ericsson |
| R2-2103801 | Clarification of mcg-RB-config field description | Ericsson |
| R2-2103802 | Clarification of mcg-RB-config field description | Ericsson |
| R2-2104528 | Summary of [AT113bis-e][007][NR15] Inter-Node | Ericsson |
| R2-2104539 | Clarification on scellFrequenciesSN | Nokia |
| R2-2104540 | Clarification on scellFrequenciesSN | Nokia |
| 5.4.1.3 | Other | |
| R2-2102903 | Clairifcation on SCell without SSB | OPPO |
| R2-2102904 | Clairifcation on SCell without SSB | OPPO |
| R2-2102905 | Clairifcation on field descritpion of SMTC in ReconfigurationWithSync for NR-DC | OPPO |
| R2-2102906 | Clairifcation on field descritpion of SMTC in ReconfigurationWithSync for NR-DC | OPPO |
| R2-2102907 | Clairifcation on usage of SMTC in the measObjectNR if not configured | OPPO |
| R2-2102908 | Clairifcation on usage of SMTC in the measObjectNR if not configured | OPPO |
| R2-2103643 | Clarification of CSI measurement configuration | Ericsson |
| R2-2103644 | Clarification of CSI measurement configuration | Ericsson |
| R2-2103877 | Clarification on CGI reporting | Apple |
| R2-2103878 | Clarification on CGI reporting | Apple |
| R2-2104279 | Discussion on ambiguity of cell ID in RAN sharing | vivo |
| R2-2104522 | Report of [AT113bis-e][008][NR15] Other & LTE (OPPO) | OPPO |
| R2-2104595 | Clarification on CGI reporting | Apple |
| R2-2104596 | Clarification on CGI reporting | Apple |
| 5.4.2 | LTE changes related to NR | |
| R2-2102770 | Report for [Post113-e][008][NR15] | Nokia, Nokia Shanghai Bell |
| R2-2104234 | Clarification on RRC full config for intra-SN PSCell change | NTT DOCOMO, INC., Ericsson, Fujitsu, Huawei, HiSilicon |
| R2-2104238 | Clarification on RRC full config for intra-SN PSCell change | NTT DOCOMO, INC., Ericsson, Fujitsu, Huawei, HiSilicon |
| R2-2104538 | LS on RI bit width for Cat5 UE in EN-DC mode | RAN2 |
| 5.4.3 | UE capabilities | |
| R2-2102610 | Reply LS on the use of simultaneous CSI-RS resources and ports (R1-2101962; contact: Ericsson) | RAN1 |
| R2-2102618 | LS on Interpretation of UE Features in Case of Cross-Carrier Operation (R1-2102085; contact: ZTE) | RAN1 |
| R2-2102623 | LS on numerology for active DL and UL BWPs (R1-2102152; contact: MediaTek) | RAN1 |
| R2-2102644 | LS to RAN2 on single-uplink operation in more than one band pair of a band combination (R4-2103144; contact: MediaTek) | RAN4 |
| R2-2103025 | CR on UE capability in case of Cross-Carrier operation | ZTE Corporation, Sanechips, Ericsson |
| R2-2103026 | CR on UE capability in case of Cross-Carrier operation | ZTE Corporation, Sanechips, Ericsson |
| R2-2103115 | Correction on Numerology for Active DL and UL BWPs Rel-15 | CATT |
| R2-2103116 | Correction on Numerology for Active DL and UL BWPs Rel-16 | CATT |
| R2-2103633 | Support of more than one singleUL per band combination | Nokia, Nokia Shanghai Bell |
| R2-2103634 | Correction to BWP capabilities | Nokia, Nokia Shanghai Bell |
| R2-2103635 | Correction to BWP capabilities | Nokia, Nokia Shanghai Bell |
| R2-2103759 | Correction to the use of simultaneous CSI-RS resources | Ericsson, Nokia |
| R2-2103760 | Correction to the use of simultaneous CSI-RS resources | Ericsson, Nokia |
| R2-2103761 | Remaining aspects for definition of fallback per CC feature set | Ericsson |
| R2-2103762 | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | Ericsson |
| R2-2103763 | Ambiguity in fr1-fr2-Add-UE-NR-Capabilities parameter | Ericsson |
| R2-2103768 | Summary of [Post113-e][051][NR15] DL scheduling slot offset | Ericsson |
| R2-2103769 | Open issues K0 configuration and use | Ericsson |
| R2-2103770 | Introduction of DL scheduling slot offset capabilities in UERadioPagingInformation | Ericsson |
| R2-2103771 | Introduction of DL scheduling slot offset capabilities in UERadioPagingInformation | Ericsson |
| R2-2103791 | Correction on bwp-DiffNumerology | ZTE Corporation, Sanechips |
| R2-2103792 | Correction on bwp-DiffNumerology | ZTE Corporation, Sanechips |
| R2-2103799 | Configuration of common fields in dedicated signalling | Ericsson |
| R2-2104021 | CR on numerology for active DL and UL BWPs | Huawei, HiSilicon |
| R2-2104022 | CR on numerology for active DL and UL BWPs | Huawei, HiSilicon |
| R2-2104023 | Clarification on the simultaneousRxTxInterBandCA capability in NR-DC | Huawei, HiSilicon |
| R2-2104024 | Clarification on the simultaneousRxTxInterBandCA capability in NR-DC | Huawei, HiSilicon |
| R2-2104025 | Discussion on BCS of a fallback band combination | Huawei, HiSilicon |
| R2-2104026 | Clarification on BCS of a fallback band combination | Huawei, HiSilicon |
| R2-2104027 | Clarification on BCS of a fallback band combination | Huawei, HiSilicon |
| R2-2104028 | Draft LS on BCS of a fallback band combination | Huawei, HiSilicon |
| R2-2104029 | Discussion on single-uplink operation in more than one band pair of a BC | Huawei, HiSilicon, Ericsson |
| R2-2104030 | Discussion on contiguous and non-contiguous for intra-band EN-DC | Huawei, HiSilicon |
| R2-2104084 | Discussion on SUO capability in more than one band pair of a BC | MediaTek Inc. |
| R2-2104087 | Reply LS on single-uplink operation in more than one band pair of a band combination | MediaTek Inc. |
| R2-2104096 | Missing support of maximum DRB number | Huawei, HiSilicon |
| R2-2104098 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
| R2-2104101 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
| R2-2104185 | Clarification on the Intra-band and Inter-band EN-DC Capabilities | ZTE Corporation, Sanechips |
| R2-2104186 | CR on the Intra-band and Inter-band EN-DC Capabilities-R15 | ZTE Corporation, Sanechips |
| R2-2104187 | CR on the Intra-band and Inter-band EN-DC Capabilities-R16 | ZTE Corporation, Sanechips |
| R2-2104188 | Draft LS on the Intra-band and Inter-band EN-DC Capabilities | ZTE Corporation, Sanechips |
| R2-2104212 | Further Clarification on the supportedBandwidthCombinationSet | ZTE Corporation, Sanechips |
| R2-2104213 | CR on the supportedBandwidthCombinationSet-R15 | ZTE Corporation, Sanechips |
| R2-2104214 | CR on the supportedBandwidthCombinationSet-R16 | ZTE Corporation, Sanechips |
| R2-2104232 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
| R2-2104233 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
| R2-2104257 | IMS video capabilities | Google Inc. |
| R2-2104258 | IMS video capabilities | Google Inc. |
| R2-2104259 | IMS video capabilities | Google Inc. |
| R2-2104260 | IMS video capabilities | Google Inc. |
| R2-2104281 | IMS video capabilities | Google Inc. |
| R2-2104283 | IMS video capabilities | Google Inc. |
| R2-2104355 | Draft LS on BCS for contiguous and non-contiguous intra-band (NG)EN-DC | Huawei, HiSilicon |
| R2-2104357 | LS on BCS for contiguous and non-contiguous intra-band (NG)EN-DC | RAN2 |
| R2-2104511 | Summary of [AT113bis-e][010][NR15] UE caps DL scheduling slot offset | Ericsson |
| R2-2104545 | Email discussion summary of [AT113bis-e][011][NR15] UE caps III (ZTE) | ZTE Corporation |
| R2-2104546 | CR on the supportedBandwidthCombinationSet-R15 | ZTE Corporation, Sanechips |
| R2-2104547 | CR on the supportedBandwidthCombinationSet-R16 | ZTE Corporation, Sanechips |
| R2-2104550 | LS on the Intra-band and Inter-band (NG)EN-DC/NE-DC Capabilities | RAN2 |
| R2-2104556 | Report of e-mail discussion [AT113bis-e][012][NR15] UE caps IV (Mediatek) | Mediatek |
| R2-2104557 | Reply LS on single-uplink operation in more than one band pair of a band combination | RAN2 |
| R2-2104558 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
| R2-2104559 | Clarification on SCS of active DL and UL BWP | MediaTek Inc. |
| R2-2104573 | Correction to BWP capabilities | Nokia, Nokia Shanghai Bell |
| R2-2104574 | Correction to BWP capabilities | Nokia, Nokia Shanghai Bell |
| R2-2104598 | Summary of [AT113bis-e][009][NR15] UE caps BCS EN-DC (Huawei) | Huawei, HiSilicon |
| R2-2104603 | LS on fallback applicability for UE FeatureSetDownLinkPerCC capability fields | RAN2 |
| R2-2104607 | CR on UE capability in case of Cross-Carrier operation | ZTE Corporation, Sanechips, Ericsson |
| R2-2104608 | CR on UE capability in case of Cross-Carrier operation | ZTE Corporation, Sanechips, Ericsson |
| R2-2104609 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
| R2-2104610 | UL Config Grant capability differentiation for FR1(TDD/FDD) / FR2 | Qualcomm Incorporated |
| 5.5 | Positioning corrections | |
| R2-2103219 | Correction on SUPL support of positioning methods | Samsung |
| R2-2103220 | Correction on SUPL support of positioning methods | Samsung |
| R2-2104512 | Report of [AT113b-e][602][POS] Positioning corrections for NR Rel-15 (Samsung) | Samsung |
| 6.1 | Common | |
| R2-2104618 | Clarifications on the TRP definition for positioning | Xiaomi Communications |
| R2-2104642 | Report of [AT113bis-e][014][NR16] Stage-2 (Xiaomi | Xiaomi Communications |
| 6.1.1 | Organisational | |
| R2-2102612 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#104-e (R1-2102007; contact: NTT DOCOMO, AT&T) | RAN1 |
| R2-2102616 | LS on uplink Tx switching (R1-2102058; contact: China Telecom) | RAN1 |
| R2-2102662 | Reply LS on UTRAN UE capabilities from CN to gNB (S2-2101596; contact: Qualcomm) | SA2 |
| R2-2102675 | LS Reply on QoS Monitoring for URLLC (S5-211350; contact: Intel) | SA5 |
| R2-2102677 | Reply LS on 3GPP NR Rel-16 URLLC and IIoT performance evaluation (RP-210884; contact: Ericsson) | RAN |
| 6.1.2.1 | TS 3x.300 | |
| R2-2102609 | Reply LS on multi-TRP description in Stage-2 (R1-2101924; contact: Nokia) | RAN1 |
| R2-2103048 | Addition of size limitation for SRVCC | Ericsson |
| R2-2103636 | Updated Multi-TRP Stage-2 description | Nokia (rapporteur) |
| R2-2103640 | Updated Multi-TRP Stage-2 description | Nokia (rapporteur) |
| R2-2103880 | Clarification on NR-U deployment scenarios | Apple |
| R2-2104172 | Missing IAB SA mode for QoS description | Samsung R&D Institute UK |
| R2-2104208 | Discussion on 2-step release with redirect without anchor change | ZTE corporation, Sanechips |
| R2-2104209 | Draft stage-2 CR for 2-step release with redirection without anchor change | ZTE corporation, Sanechips |
| R2-2104218 | Clarifications on the TRP definition for eMIMO and positioning | Xiaomi Communications, Samsung, OPPO |
| R2-2104219 | Clarifications on the TRP definition for eMIMO and positioning | Xiaomi Communications, Samsung, OPPO, ZTE Corporation |
| R2-2104252 | Draft LS on 2-step release with redirect without anchor change | ZTE corporation, Sanechips |
| R2-2104617 | Addition of size limitation for SRVCC | Ericsson, Nokia |
| R2-2104647 | Missing IAB SA mode for QoS description | Samsung R&D Institute UK |
| 6.1.2.2 | TS 37.340 | |
| R2-2103557 | Clarification on IP packet type in DedicatedInfoF1c | Nokia, Nokia Shanghai Bell |
| R2-2104015 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT, IAB | ZTE Corporation(Rapporteur) |
| R2-2104611 | Miscellaneous corrections on DCCA, 2-step RACH, IIOT, IAB | ZTE Corporation(Rapporteur) |
| 6.1.3.1 | MAC | |
| R2-2102626 | Reply LS on overlapped data and SR are of equal L1 priority (R1-2102244; contact: vivo) | RAN1 |
| R2-2102628 | LS on UL skipping for PUSCH in Rel-16 (R1-2102249; contact: vivo) | RAN1 |
| R2-2102723 | Autonomous transmission and bundling | CATT |
| R2-2102724 | Analysis of RAN1 reply LS on overlapped SR and data | CATT |
| R2-2102754 | Draft reply LS to RAN1 on overlapped data and SR are of equal L1 priority | vivo |
| R2-2102759 | Remaining issues on overlapped PUSCH and UCI with UL skipping | vivo |
| R2-2102763 | Clarification on which uplink grants participate to the intra-UE prioritization procedure | CATT, Samsung, Ericsson |
| R2-2102764 | Stop ongoing Random Access procedure due to pre-emptive BSR | CATT |
| R2-2102774 | CG Bundle Configured with AutonomousTx | Samsung |
| R2-2102775 | Discussion on overlapped data and SR with equal PHY priority | Samsung |
| R2-2102776 | UL Skipping with LCH-based Prioritization | Samsung |
| R2-2102777 | NDI Toggling Status Update for CG Retransmission | Samsung |
| R2-2102778 | CG Bundle Configured with LCH-based Prioritization | Samsung |
| R2-2102791 | Corrections on MAC handling of uplink grants within a bundle | CATT |
| R2-2102845 | Discussion on CGT handling in the case of autonomous transmission and bundling | Huawei, HiSilicon |
| R2-2103023 | Corrections to BSR/PHR content for NR-U | ZTE Corporation, Sanechips |
| R2-2103067 | LCH based prioritization for SR and PUSCH | Intel Corporation |
| R2-2103208 | Discussion on reply LS on overlapped data and SR are of equal L1 priority | OPPO |
| R2-2103293 | CR for not transmitting only padding and padding BSR with eLCID | Samsung |
| R2-2103366 | Correction to PUSCH skipping with UCI for NR-U | Nokia, Nokia Shanghai Bell |
| R2-2103381 | Correction to PUSCH skipping with UCI for NR-U | Nokia, Nokia Shanghai Bell |
| R2-2103426 | Remaining corrections for Intra-UE prioritization | Ericsson |
| R2-2103427 | CG timer handling upon de-prioritization of bundled PUSCH | Ericsson |
| R2-2103435 | Consideration on the CGT behavior for CG bundling transmission | ZTE Corporation, Sanechips |
| R2-2103436 | Correction of 38.321 on priority handling for bundling CG transmission | ZTE Corporation, Sanechips |
| R2-2103437 | Reconsideration on timer control when performing configured grant transmission | ZTECorporation, Sanechips |
| R2-2103438 | Correction to 38.321 on the timer control when performing the CG transmission | ZTE Corporation, Sanechips |
| R2-2103439 | Considerations on the intra-UE multiplexing coupled with PUCCH transmission | ZTE Corporation, Sanechips |
| R2-2103440 | Correction to 38.321 on intra-UE multipexing involved PUCCH transmission | ZTE Corporation, Sanechips |
| R2-2103447 | Discussion on SCell BFR regarding RS change | ASUSTeK |
| R2-2103481 | MAC behaviour for overlapped UCI(s), SR and PUSCH with equal L1 priority | Huawei, HiSilicon |
| R2-2103534 | Correction to RA-RNTI generation for 2-step RA | Huawei, HiSilicon |
| R2-2103845 | UL skipping and intra-UE prioritization | Apple |
| R2-2103846 | Overlapped SR and PUSCH of equal L1 priority | Apple |
| R2-2103847 | Treatment of overlapping SR/Data | Apple |
| R2-2103959 | Report of [Post113-e][052][NR16] cgRetxTimer (Qualcomm) | Qualcomm Incorporated |
| R2-2104054 | RAN2 impact of Case 1-6 for UL skipping | Huawei, HiSilicon |
| R2-2104104 | Clarification on HARQ status upon LBT failure | LG Electronics UK, Ericsson |
| R2-2104216 | IIOT/URLLC co-existence in Rel-16 | LG Electronics UK |
| R2-2104217 | IIOT NR-U co-existence in Rel-16 | LG Electronics UK |
| R2-2104309 | Treatment of overlapping SR/Data | Apple |
| R2-2104541 | Corrections on MAC handling of uplink grants within a bundle | CATT |
| R2-2104544 | Report of Offline 016: MAC II (Samsung) | Samsung |
| R2-2104631 | Report of [AT113bis-e][015][NR16] Overlapping UCI Data and SR | vivo |
| 6.1.3.2 | RLC | |
| R2-2102943 | RETX_COUNT upon expiry of t-PollRetransmit | Nokia, Nokia Shanghai Bell |
| 6.1.3.3 | PDCP | |
| R2-2102630 | LS on synchronization of Ethernet Compression (R3-211128; contact: Nokia) | RAN3 |
| R2-2102846 | Potential issues on synchronization of EHC | Huawei, HiSilicon |
| R2-2103590 | Response to RAN3 LS on state synchronization of EHC | ZTE Corporation, Sanechips |
| R2-2104203 | PDCP miscellaneous corrections | LG Electronics Inc. (PDCP rapporteur) |
| R2-2104619 | [DRAFT] Reply LS on synchronization of Ethernet Compression | Nokia |
| R2-2104643 | Reply LS on synchronization of Ethernet Compression | RAN2 |
| 6.1.3.5 | BAP | |
| R2-2103935 | Handling of Unknown and Reserved Values in the BAP Header | Ericsson, AT&T |
| R2-2104165 | Miscellaneous corrections on BAP transmitting operation and default routing | Huawei, HiSilicon (Rapporteur) |
| R2-2104560 | Miscellaneous corrections on BAP transmitting operation and default routing | Huawei, HiSilicon (Rapporteur) |
| 6.1.4.1.1 | Connection control | |
| R2-2102854 | Correction on repetition for L1-SINR | vivo |
| R2-2103209 | CR on the configuration restriction on DCI format 0_2/1_2 for unlicensed band (Option 1) | OPPO, Samsung, Xiaomi, ZTE, Apple, Intel |
| R2-2103210 | CR on the UE capability restriction on DCI format 0_2/1_2 for unlicensed band (Option 2) | OPPO, Samsung, Xiaomi |
| R2-2103280 | Correction on description of ssb-PositionsInBurst in ServingCellConfigCommonSIB | Fujitsu |
| R2-2103449 | Correction on freqMonitorLocations | ASUSTeK |
| R2-2103937 | Clarification to BAP address field description in the BAP-RoutingID IE | Ericsson |
| R2-2104167 | Miscellaenous corrections on BH RLC channel management for IAB-MT | Huawei, HiSilicon |
| R2-2104240 | Correction on description of subCarrierSpacing in BWP | Fujitsu, Samsung |
| R2-2104247 | Correction on releasing referenceTimePreferenceReporting and sl-AssistanceConfigNR | Google Inc. |
| R2-2104562 | Miscellaenous corrections on BH RLC channel management for IAB-MT | Huawei, HiSilicon |
| R2-2104585 | Report of [Offline-019][NR16] Connection Control | Fujitsu |
| R2-2104604 | Correction on description of subCarrierSpacing in BWP | Fujitsu, Samsung |
| R2-2104605 | Correction on description of ssb-PositionsInBurst in ServingCellConfigCommonSIB | Fujitsu |
| 6.1.4.1.2 | RRM and Measurements | |
| R2-2102650 | LS on CGI reading with autonomous gaps (R4-2103610; contact: ZTE) | RAN4 |
| R2-2103030 | Correction on T321 for autonomous gap based E-UTRAN CGI reporting | ZTE Corporation, Sanechips |
| R2-2103169 | Clarification on NPN related CGI report | Huawei, CMCC, China Telecom, China Unicom, HiSilicon |
| R2-2103281 | Discussion on configuration of SSBs to be measured for NR-U | Fujitsu |
| R2-2103879 | Discussion on NR-U RRM measurement | Apple, xiaomi, LG Electronics |
| R2-2104173 | Missing smtc3 for smtc restriction with ssbFrequency | Samsung R&D Institute UK |
| R2-2104591 | Summary of [Offline-020][NR16] RRM and Measurements (Apple | Apple |
| R2-2104592 | Inter-RAT RRM measurement on NR-U | Apple, Fujitsu, xiaomi, LG Electronics |
| R2-2104593 | SSB-ToMeasure for NR-U | Apple, Fujitsu, xiaomi, LG Electronics |
| R2-2104594 | LS to RAN1 on random value generation for RMTC-SubframeOffset | RAN2 |
| R2-2104623 | Summary of [Offline-020][NR16] RRM and Measurements (Apple | Apple |
| 6.1.4.1.3 | System Information and Paging | |
| R2-2102714 | Corrections to UE action upon SIB1 reception | Samsung Electronics Co., Ltd |
| R2-2103061 | Reported BCS when IE intraBandENDC-support is set to “both” | T-Mobile USA Inc. |
| R2-2103582 | Discussion on leap second and DST for R16 accurate time | ZTE Corporation, Sanechips |
| R2-2104506 | Discussion on leap second and DST for R16 accurate time | ZTE Corporation, Sanechips, CMCC, China Southern Power Grid Co., Ltd |
| R2-2104529 | Summary of [AT113bis-e][021][NR16] Sys Info Inter Node and Misc | Ericsson |
| R2-2104568 | Corrections to UE action upon SIB1 reception | Samsung Electronics Co., Ltd |
| 6.1.4.1.4 | Inter-Node RRC messages | |
| R2-2103661 | Introducing the UE config release in INM | Ericsson |
| R2-2103851 | Correction on UTRA Capabilty forwarding in HO preparation | Apple |
| R2-2103929 | Correction on failureType in FailureReportSCG-EUTRA and scgFailureInfoEUTRA | Huawei, HiSilicon |
| R2-2104205 | Introduction of TDD Configuration Inter-node RRC Message | CATT |
| R2-2104543 | Correction on failureType in FailureReportSCG-EUTRA and scgFailureInfoEUTRA | Huawei, HiSilicon, Ericsson |
| 6.1.4.1.5 | Other | |
| R2-2103042 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2103043 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2103044 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2103045 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2103204 | Conditional handover and UAI/SUI | MediaTek Inc., Ericsson, Sharp, LG Electronics |
| R2-2103464 | RRC processing delays for combined procedures | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2103467 | On combined RRC procedures | Nokia, Nokia Shanghai Bell, Ericsson |
| R2-2103623 | Clarification on the initiation of RNA update | Huawei, HiSilicon |
| R2-2103624 | Clarification on RRC Release cause for inter-RAT cell (re)selection in RRC_INACTIVE | Huawei, HiSilicon |
| R2-2103645 | Miscellaneous non-controversial corrections Set IX | Ericsson |
| R2-2103936 | Correction to scgFailureInfoEUTRA and FailureReportSCG-EUTRA | Ericsson |
| R2-2104620 | Clarification on the initiation of RNA update | Huawei, HiSilicon |
| R2-2104621 | Clarification on the initiation of RNA update | Huawei, HiSilicon |
| R2-2104634 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2104635 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2104636 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2104637 | Redirection with MPS Indication | Perspecta Labs, CISA ECD, T-Mobile, Ericsson, Qualcomm |
| R2-2104641 | Report of [AT113bis-e][001][TEI16] TEI16 new and small | Mediatek Inc. |
| R2-2104650 | Miscellaneous non-controversial corrections Set X | Ericsson |
| R2-2104651 | Miscellaneous non-controversial corrections Set X | Ericsson |
| 6.1.4.2 | LTE changes | |
| R2-2102800 | Clarification on DLInformationTransfer and ULInformationTransfer | CATT |
| R2-2103558 | Clarification on IP packet type in DedicatedInfoF1c | Nokia, Nokia Shanghai Bell |
| R2-2103598 | Transfer of F1C traffic over LTE leg in IAB - Option A | Samsung Electronics GmbH |
| R2-2103601 | Transfer of F1C traffic over LTE leg in IAB - Option B | Samsung Electronics GmbH |
| R2-2104166 | Miscellaneous corrections for TS 36.331 on F1 over LTE for IAB | Huawei, HiSilicon |
| R2-2104177 | Correction on ULInformationTransfer failure handling for IAB in 36.331 [Opt A] | Samsung R&D Institute UK |
| R2-2104178 | Correction on ULInformationTransfer failure handling for IAB in 36.331 [Opt B] | Samsung R&D Institute UK |
| R2-2104513 | Discussion summary (Phase 1) - [AT113bis-e][022][NR16] IAB LTE Changes (Samsung) | Samsung |
| R2-2104561 | Miscellaneous corrections for TS 36.331 on F1 over LTE for IAB | Huawei, HiSilicon, Samsung Electronics GmbH |
| R2-2104597 | IAB LTE changes | Samsung |
| 6.1.4.3 | UE capabilities | |
| R2-2102646 | LS on Signalling scheme of Transparent TxD (R4-2103360; contact: vivo) | RAN4 |
| R2-2102647 | LS on Rel-16 updated RAN4 UE features lists for LTE and NR (R4-2103368; contact: CMCC) | RAN4 |
| R2-2102868 | Miscellaneous corrections to Rel-16 UE capabilities | Intel Corporation |
| R2-2102879 | Correction on Capability of two PUCCH transmission | OPPO |
| R2-2103137 | Correction on IAB in TS 38.306 | ZTE, Sanechips |
| R2-2103187 | Discussion on RAN4 LS on signalling scheme of transparent TxD | vivo |
| R2-2103312 | [Draft] Reply LS to RAN4 on the capability of transparent TxD | vivo |
| R2-2103313 | CR on 38.306 for the capability of supporting txDiversity-r16 | vivo |
| R2-2103314 | CR on 38.331 for the capability of supporting txDiversity-r16 | vivo |
| R2-2103315 | CR on 38.306 for the release independent capability of txDiversity | vivo |
| R2-2103316 | CR on 38.331 for the release independent capability of txDiversity | vivo |
| R2-2103637 | UE capability for transmit diversity testing | Nokia, Nokia Shanghai Bell |
| R2-2103638 | UE capability for transmit diversity testing | Nokia, Nokia Shanghai Bell |
| R2-2103669 | Support of MAC subheaders with one-octet eLCID field | Lenovo, Motorola Mobility |
| R2-2103734 | UE Feature list for NR Rel-16 | Intel Corporation |
| R2-2103764 | Correction to Multi-PUSCH UL grant | Ericsson |
| R2-2103765 | Transparent TxD Capability and Signaling | Ericsson |
| R2-2104031 | Discussion on transparent TxD capability | Huawei, HiSilicon |
| R2-2104353 | Reply LS to RAN4 on the capability of transparent TxD | RAN2 |
| R2-2104553 | Miscellaneous corrections to Rel-16 UE capabilities | Intel Corporation |
| R2-2104554 | UE Feature list for NR Rel-16 | Intel Corporation |
| R2-2104555 | [AT113bis-e][023][NR16] Summary of UE Caps (Intel) | Intel |
| R2-2104569 | Correction on Capability of two PUCCH transmission | OPPO |
| R2-2104612 | Summary of offline discussion #030: Signalling scheme of Transparent TxD | vivo |
| R2-2104613 | CR on 38.306 for the capability of supporting txDiversity-r16 | vivo |
| R2-2104614 | [Draft] Reply LS to RAN4 on the capability of transparent TxD | vivo |
| 6.1.4.4 | Idle/inactive mode procedures | |
| R2-2102910 | Discussion on RNA configuration for UE in SNPN AM | Samsung Electronics Co., Ltd |
| R2-2102930 | Removal of duplicated statements related to IFRI handling | LG Electronics France |
| R2-2103168 | CR on the missing definition of Available SNPN in TS 38.304 | Huawei, HiSilicon |
| R2-2104521 | Discussion summary of [AT113bis-e][024][NR16] Idle Inactive | Huawei (Rapporteur) |
| R2-2104537 | Correction on RNA configuration for UE in SNPN access mode | Samsung |
| 6.2 | NR V2X | |
| R2-2104510 | Offline 002 on Stage 2 Corrections | Nokia (Rapporteur) |
| 6.2.1 | General and Stage-2 corrections | |
| R2-2102604 | Reply LS on the re-keying procedure and security indication for NR SL (C1-211228; contact: Nokia) | CT1 |
| R2-2102614 | Reply LS on per-table MCS range for mode-2 (R1-2102017; contact: OPPO) | RAN1 |
| R2-2102615 | Reply LS on SL switching priority (R1-2102034; contact: Xiaomi) | RAN1 |
| R2-2102622 | LS on maximum data rate for NR sidelink (R1-2102137; contact: Samsung) | RAN1 |
| R2-2102624 | LS on SL HARQ-ACK reporting to the gNB (R1-2102176; contact: Ericsson) | RAN1 |
| R2-2102668 | Reply LS on confirming the layer to provide security (S3-210738; contact: Huawei) | SA3 |
| R2-2102880 | Correction on V2X UE capability | OPPO |
| R2-2104107 | Clarification on LTE DAPS and sidelink on 36.300 | Huawei, HiSilicon |
| R2-2104460 | Correction on V2X UE capability | OPPO |
| 6.2.2 | Control plane corrections | |
| R2-2102712 | Corrections to usage of CG Type 2 when T310 is running | Samsung Electronics Co., Ltd |
| R2-2102713 | Corrections to usage of exceptional pool during handover | Samsung Electronics Co., Ltd |
| R2-2102881 | Left issue on synchronization of PSSCH vs. PSFCH | OPPO, Ericsson, Apple, Nokia, Nokia Shanghai Bell |
| R2-2102984 | Correction on sidleink configuration | ZTE Corporation, Sanechips |
| R2-2102985 | Correction on sidelink reset operation | ZTE Corporation, Sanechips |
| R2-2102986 | Discussion on sidelink reset operation | ZTE Corporation, Sanechips |
| R2-2103090 | Miscellaneous Correction on TS38 331 | CATT |
| R2-2103127 | Miscellaneous corrections on NR V2X | SHARP Corporation |
| R2-2103172 | Addition of total L2 buffer size and RLC RTT for NR SL in TS 38.306 | Huawei, HiSilicon |
| R2-2103317 | Corrections related to SA3 and RAN1 | vivo |
| R2-2103318 | CR on the inter-frequency sidelink operation | vivo |
| R2-2103500 | Correction of Sidelink Configured Grant Usage During Handover | Nokia Germany |
| R2-2103502 | Clarification of Sidelink Configured Grant Validity under Handover Failure | Nokia Germany |
| R2-2103767 | On the peer UE capability transfer in unicast sidelink | Nokia, Nokia Shanghai Bell |
| R2-2104105 | Miscellaneous corrections on TS 38.331 (Rapporteur CR) | Huawei, HiSilicon |
| R2-2104108 | Miscellaneous corrections on TS 36.331 (Rapporteur CR) | Huawei, HiSilicon |
| R2-2104109 | Summary of [POST113-e][706][V2X] RRC impacts from the latest RAN1 decisions | Huawei, HiSilicon |
| R2-2104110 | Correction on TS 38.331 from the latest RAN1 decisions | Huawei, HiSilicon |
| R2-2104111 | Corrections on MCS selection | Huawei, HiSilicon |
| R2-2104112 | Reply LS to RAN1 on SL HARQ-ACK reporting to the gNB | Huawei, HiSilicon |
| R2-2104294 | Summary of CP corrections in AI 6.2.2 | Huawei, HiSilicon |
| R2-2104461 | Correction on TS 38.331 from the latest RAN1 decisions | Huawei, HiSilicon |
| R2-2104462 | Corrections on MCS selection | Huawei, HiSilicon |
| R2-2104463 | Reply LS to RAN1 on SL HARQ-ACK reporting to the gNB | RAN2 |
| R2-2104464 | Miscellaneous corrections on TS 38.331 (Rapporteur CR) | Huawei, HiSilicon |
| R2-2104465 | Miscellaneous corrections on TS 36.331 (Rapporteur CR) | Huawei, HiSilicon |
| R2-2104466 | [AT113bis-e][702][V2X/SL] Miscellaneous corrections on RRC | Huawei (Rapporteur) |
| R2-2104467 | Corrections to usage of exceptional pool during handover | Samsung Electronics Co., Ltd |
| R2-2104468 | [AT113bis-e][703][V2X/SL] Correction of SL CG during Handover | Nokia, Nokia Shanghai Bell |
| R2-2104469 | Summary of [704] | OPPO |
| 6.2.3 | User plane corrections | |
| R2-2102722 | Summary of [POST113-e][707][V2X] Spec update to level 3 logical slots | OPPO |
| R2-2102731 | 38321CR on correction of SL configured grant | OPPO |
| R2-2102732 | 38331 CR on correction of SL configured grant | OPPO |
| R2-2102748 | Discussion on Tx-resource (re)selection with HARQ feedback consideration | OPPO |
| R2-2102812 | Clarification on sidelink process ID in SCI | vivo |
| R2-2102813 | Alignment with RAN1 on TX resource (re-)selection | vivo, ZTE |
| R2-2102814 | Draft LS to RAN1 on the minimum gap ensuring issue | vivo |
| R2-2102882 | Left issue on PUCCH reporting | OPPO |
| R2-2102883 | Correction on SL buffer flushing for sl-MaxTransNum | OPPO |
| R2-2102884 | Correction on sl-MaxTransNum configurable value | OPPO |
| R2-2102885 | Summary of [POST113-e][708] How to handle DG for retransmissions | OPPO |
| R2-2102983 | Correction on HARQ feedback of CSI report MAC CE | ZTE Corporation, Sanechips |
| R2-2102995 | Correction on TS 38.321 for mode 2 UE performing re-evaluation check | OPPO |
| R2-2102996 | How to handle dynamic grant for retransmissions | Ericsson |
| R2-2102997 | Correction of PQFI terminology in SDAP – Alt. 1 | Ericsson |
| R2-2102998 | Correction of PQFI terminology in SDAP – Alt. 2 | Ericsson |
| R2-2102999 | Correction of PQFI terminology in RRC spec – Alt. 2 | Ericsson |
| R2-2103091 | Miscellaneous Correction on TS38 321 | CATT |
| R2-2103092 | TX Resource (Re)Selection with HARQ Feedback Consideration | CATT |
| R2-2103117 | Correction on SL HARQ-ACK reporting on sidelink | SHARP Corporation |
| R2-2103282 | Correction on Buffer Size description of SL-BSR MAC CE | Fujitsu |
| R2-2103296 | CR for field descriptions of MAC subheader | Samsung |
| R2-2103379 | Corrections on UL/SL Prioritization Condition | CATT |
| R2-2103380 | Corrections on Resource Reservation for Mode2 | CATT |
| R2-2103850 | Correction on the usage of sl-ReselectAfter | Apple |
| R2-2104106 | Handling of the retransmission TB without an assocaited SL process | Huawei, HiSilicon |
| R2-2104470 | Miscellaneous MAC corrections | LG Electronics Inc. |
| R2-2104471 | [AT113-e][710][V2X/SL] Miscellaneous MAC corrections (LG) | LG Electronics Inc. (Rapporteur) |
| R2-2104475 | LS on R16 V2X for PUCCH reporting and for minimum time gap | RAN2 |
| R2-2104493 | Review Report on MAC CRs in AI 6.2.3 | LG Electronics Inc. (Rapporteur) |
| R2-2104542 | Correction of PQFI terminology in SDAP – Alt. 1 | Ericsson |
| 6.3.1 | General and Stage 2 corrections | |
| R2-2103922 | UE handling of Positioning Frequency Layer | Ericsson |
| R2-2104018 | Summary of agenda item 6.3.1 - REL-16 NR Positioning Stage 2 | Nokia, Nokia Shanghai Bell |
| R2-2104046 | Correction to NR stage2 spec for MO-LR | Huawei, HiSilicon |
| R2-2104047 | Correction to LTE stage2 spec for MO-LR | Huawei, HiSilicon |
| R2-2104048 | Correction to 5G support for NB-IOT positioning | Huawei, HiSilicon |
| R2-2104407 | Correction to 5G support for NB-IOT positioning | Huawei, HiSilicon |
| R2-2104409 | [DRAFT] LS on mobile-originated location request | Huawei, HiSilicon |
| R2-2104527 | Correction to NR stage2 spec for MO-LR | Huawei, HiSilicon |
| 6.3.2 | RRC corrections | |
| R2-2102924 | Corrections on the description of SRS-Config | CATT |
| R2-2103849 | Correction on the SI offset usage of posSI Scheduling | Apple |
| R2-2103919 | Same posSIB-Type in multiple SI messages | Ericsson |
| R2-2103920 | Summary for RRC NR Positioning | Ericsson |
| R2-2104175 | Correction on posSI-RequestConfig and posSI-RequestConfigSUL field description | Samsung R&D Institute UK |
| R2-2104408 | Corrections on the description of SRS-Config | CATT |
| R2-2104410 | Correction for the positioning SI offset and clarification on mapping of posSIB to SI | Ericsson, Apple |
| R2-2104576 | [AT113bis-e][606][POS] Positioning RRC open issues (Ericsson) | Ericsson |
| 6.3.3 | LPP corrections | |
| R2-2102786 | 37.355 Draft CR on timestamp reference in NR positioning measurement report | vivo |
| R2-2102920 | Corrections on the field description of NR-AdditionalPathList and DL-PRS positioning frequency layer related parameters | CATT |
| R2-2102921 | Corrections on NR-Multi-RTT-RequestAssistanceData | CATT |
| R2-2102922 | Corrections on the need code of segmentationInfo within CommonIEsRequestLocationInformation and CommonIEsProvideAssistanceData | CATT |
| R2-2102987 | Considerations on missing need codes in LPP | Lenovo, Motorola Mobility |
| R2-2103129 | Summary of AI 6.3.3 LPP corrections | CATT |
| R2-2103921 | LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap | Ericsson |
| R2-2103923 | Need of compact expirationTime Indication | Ericsson |
| R2-2103924 | Correction of field description name | Ericsson |
| R2-2104049 | Correction to PRS configuration | Huawei, HiSilicon |
| R2-2104050 | Correction to the uplink LPP message | Huawei, HiSilicon |
| R2-2104051 | Correction to DL-PRS capability | Huawei, HiSilicon |
| R2-2104052 | Correction on positioning error reporting | Huawei, HiSilicon |
| R2-2104269 | Correction on the field description of additionPaths | ZTE Corporation, Sanechips |
| R2-2104520 | Miscellaneous corrections on the field description | CATT, Ericsson, ZTE |
| R2-2104565 | Correction to PRS configuration | Huawei, HiSilicon |
| R2-2104566 | Correction to the uplink LPP message | Huawei, HiSilicon |
| R2-2104567 | Correction to DL-PRS capability | Huawei, HiSilicon |
| R2-2104575 | LPP Layer interaction with lower layers for Positioning Frequency layer and Measurement Gap | Ericsson |
| 6.3.4 | MAC corrections | |
| R2-2102923 | Corrections on SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| R2-2104412 | Corrections on SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| R2-2104417 | Corrections on the UE capability on the extension in SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| R2-2104418 | Corrections on the UE capability on the extension in SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| R2-2104504 | Corrections on SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| R2-2104563 | Corrections on the UE capability on the extension in SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| R2-2104564 | Corrections on the UE capability on the extension in SP Positioning SRS Activation and Deactivation MAC CE | CATT |
| 6.4.1 | CHO/CPC Corrections | |
| R2-2102875 | CR on UE Information report for CHO (Option-1) | OPPO |
| R2-2102876 | CR on UE Information report for CHO (Option-1) | OPPO |
| R2-2102877 | CR on UE Information report for CHO (Option-2) | OPPO |
| R2-2102878 | CR on UE Information report for CHO (Option-2) | OPPO |
| R2-2103046 | Conditional evaluation upon fallback to source cell after DAPS handover | Ericsson |
| R2-2103047 | Conditional evaluation upon fallback to source cell after DAPS handover | Ericsson |
| R2-2103114 | Discussion on Applicable Cases for Failure Recovery via CHO | CATT |
| R2-2103215 | Conditional handover and UAI/SUI | MediaTek Inc., Ericsson, Sharp, LG Electronics, Qualcomm Incorporated |
| R2-2103331 | 38.331 CR: Revised inability to comply with conditional reconfiguration | Nokia, Nokia Shanghai Bell |
| R2-2103332 | Clarification on SCG configuration in CHO | Nokia, Nokia Shanghai Bell |
| R2-2104000 | Discussion on cross-SRB CPC reconfiguration | Huawei, HiSilicon |
| R2-2104001 | Discussion on the re-transmission of UL message after CHO execution | Huawei, HiSilicon, China Telecom |
| R2-2104074 | Miscellaneous corrections to 37.340 on mobility enhancement | ZTE Corporation (Rapporteur), Sanechips |
| R2-2104100 | Discussion on UE information transmission in CHO case | ZTE Corporation |
| R2-2104261 | Full configuration for CHO | Google Inc. |
| R2-2104311 | Summary of [AT113bis-e][210][MOB] CHO/CPC corrections (Huawei) | Huawei |
| R2-2104327 | Transmission of InDeviceCoexistence, UEAssistanceInformation, MBMSInterestIndication, or SidelinkUEInformation after conditional handover | MediaTek, Ericsson |
| R2-2104328 | Transmission of Transmission of UEAssistanceInformation or SidelinkUEInformationNR after conditional handover | MediaTek, Ericsson, Sharp, LG Electronics, Qualcomm Incorporated |
| R2-2104339 | Miscellaneous corrections to 37.340 on mobility enhancement | ZTE Corporation (Rapporteur), Sanechips, Ericsson |
| R2-2104347 | Full configuration for CHO | Google Inc. |
| R2-2104348 | LS on Conditional Handover with SCG configuration scenarios | RAN2 |
| R2-2104589 | Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | CATT |
| R2-2104590 | Correction on Failure Recovery via CHO for Inter-RAT Handover Failure | CATT |
| 6.4.2 | DAPS handover Corrections | |
| R2-2102820 | Reconfiguration during DAPS HO | Ericsson |
| R2-2102821 | Addition and release of DRBs in DAPS HO Command | Ericsson |
| R2-2102822 | Addition and release of DRBs in DAPS HO Command | Ericsson |
| R2-2103291 | CR on LCP of the source MAC entity | Samsung |
| R2-2103292 | CR on LCP of the source MAC entity | Samsung |
| R2-2103333 | 38.300 CR: Transmissions to the source that continue upon DAPS UL switching | Nokia, Nokia Shanghai Bell |
| R2-2103625 | Correction on RRC re-establishment for DAPS | Huawei, HiSilicon |
| R2-2103626 | Clarification on RLF detection of source Pcell | Huawei, HiSilicon |
| R2-2104072 | Handling of physicalCellGroupConfig in DAPS handover | MediaTek Inc. |
| R2-2104075 | CR on T312 handling in DAPS HO | ZTE Corporation, Sanechips |
| R2-2104076 | CR on configuration release in DAPS HO | ZTE Corporation, Sanechips |
| R2-2104125 | Configuration for UDCEHC and DAPS | LG Electronics Inc. |
| R2-2104128 | Configuration for EHC and DAPS | LG Electronics Inc. |
| R2-2104312 | Summary of [AT113bis-e][211][MOB] DAPS corrections (Samsung) | Samsung |
| R2-2104330 | Summary of [AT113bis-e][213][MOB] RRCReconfiguration with DAPS source release (Ericsson) | Ericsson |
| R2-2104336 | Transmissions to the source that continue upon DAPS UL switching | Nokia, Nokia Shanghai Bell |
| R2-2104337 | Clarification on RLF detection of source Pcell | Huawei, HiSilicon |
| R2-2104338 | Clarification on RLF detection of source Pcell | Huawei, HiSilicon |
| R2-2104350 | CR on configuration release in DAPS HO | ZTE Corporation, Sanechips |
| R2-2104570 | Reconfiguration during DAPS HO | Ericsson |
| R2-2104571 | Reconfiguration during DAPS HO | Ericsson |
| 6.5.1 | Corrections to Fast Scell activation and Early measurement reporting | |
| R2-2103110 | Addition of early measurement in idle/inactive UE behavior description in 38.331 | CATT |
| R2-2103111 | Addition of early measurement in idle/inactive UE behavior description in 36.331 | CATT |
| R2-2103803 | Misc corrections for Rel-16 DCCA | Ericsson |
| R2-2103804 | Misc corrections for Rel-16 DCCA | Ericsson |
| R2-2104313 | Summary of [AT113bis-e][220][DCCA] Miscellaneous DCCA corrections (Ericsson) | Ericsson |
| R2-2104342 | Misc corrections for Rel-16 DCCA | Ericsson |
| R2-2104343 | Misc corrections for Rel-16 DCCA | Ericsson |
| 6.5.2 | Other DCCA corrections | |
| R2-2102613 | Reply LS on TCI state indication at Direct SCell activation (R1-2102015; contact: MediaTek) | RAN1 |
| R2-2102648 | Further Reply LS on power control for NR-DC (R4-2103373; contact: vivo) | RAN4 |
| R2-2102874 | Correction on FR2 NR-DC power control parameter | vivo, MediaTek Inc. |
| R2-2103031 | CR on SCG release and suspend in EN-DC | ZTE Corporation, Sanechips |
| R2-2103270 | Set-up and release of T316 in procedures | Nokia, Nokia Shanghai Bell |
| R2-2103271 | NR DC power control signaling | Nokia, Nokia Shanghai Bell |
| R2-2103272 | NR DC power control signaling | Nokia, Nokia Shanghai Bell |
| R2-2103273 | NR DC Cell Grouping | Nokia, Nokia Shanghai Bell |
| R2-2103805 | Cell grouping for asynchronous NR-DC | Ericsson |
| R2-2103806 | Correction on p-UE-FR2 and p-NR-FR2 for NR-DC power control | Ericsson |
| R2-2103981 | T316 handling when the split SRB1 or SRB3 is released | Huawei, HiSilicon |
| R2-2104036 | Report of [Post113-e][224][DCCA] TCI state indication at direct SCell activation (MediaTek) | MediaTek Inc. |
| R2-2104040 | [DRAFT] Reply LS on TCI state indication at Direct Scell activation | MediaTek Inc. |
| R2-2104044 | Clarification on NR SCG configuration within RRC Resume | MediaTek Inc. |
| R2-2104139 | Clarification on intra-FR2 NR-DC power control | Huawei, HiSilicon |
| R2-2104314 | Summary of [AT113bis-e][221][DCCA] NR-DC power control signalling (Huawei) | Huawei |
| R2-2104324 | Summary of [AT113bis-e][222][DCCA] NR-DC cell grouping (NN) | NN |
| R2-2104326 | Reply LS on TCI state indication at Direct SCell activation | RAN2 |
| R2-2104344 | CR on SCG release and suspend in EN-DC | ZTE Corporation, Sanechips |
| R2-2104345 | CR on SCG release in EN-DC | ZTE Corporation, Sanechips |
| R2-2104346 | CR on SCG release in EN-DC | ZTE Corporation, Sanechips |
| R2-2104652 | Reply LS on Introduction of Cell Grouping UE capability for NR-DC (R4-2105333; contact: Qualcomm) | RAN4 |
| 6.6.1 | General and stage-2 corrections | |
| R2-2102632 | Reply LS on MDT Stage 2 and Stage 3 alignment (R3-211140; contact: Ericsson) | RAN3 |
| R2-2102641 | Reply LS on limitation of Propagation of immediate MDT configuration in case of Xn inter-RAT HO (R3-211335; contact: ZTE) | RAN3 |
| R2-2102671 | Reply LS on propagation of user consent related information during Xn inter-PLMN handover (S3-211330; contact: Ericsson) | SA3 |
| R2-2102672 | Reply LS on the user consent for trace reporting (S3-211338; contact: Qualcomm) | SA3 |
| R2-2103549 | Clarification on RAN measurements collection period | Nokia, Nokia Shanghai Bell |
| R2-2103819 | [Draft] Reply LS on MDT Stage 2 and Stage 3 alignment | Ericsson |
| R2-2104037 | Clarification on Average UE throughout measurement | Samsung |
| R2-2104199 | Correction to 37320 on MDT context handling | ZTE Corporation, Sanechips |
| R2-2104430 | Summary for 6.6.1 General and stage-2 corrections | CMCC |
| R2-2104433 | Summary for 6.6.1 General and stage-2 corrections | CMCC |
| R2-2104444 | Merged Corrections to TS 37.320 | CMCC, Nokia |
| 6.6.2 | TS 38.314 corrections | |
| R2-2103821 | On corrections to packet loss rate measurements | Ericsson |
| 6.6.3 | RRC corrections | |
| R2-2102909 | Correction on periodic logging in any cell selection state | Samsung Electronics Co., Ltd |
| R2-2102911 | Correction on RLF report content determination for EUTRA frequency measurements | Samsung Electronics Co., Ltd |
| R2-2102912 | Correction on RLF report for re-connection | Samsung Electronics Co., Ltd |
| R2-2103073 | Handling of user contest for location reporting in SONMDT | QUALCOMM Incorporated |
| R2-2103101 | Correction on Inter-RAT MRO in 38.331 | CATT |
| R2-2103766 | Clarification on LocationInfo reporting for SON | NTT DOCOMO, INC. |
| R2-2103812 | on ReconnectionCellId and timeUntilReconnection field | Ericsson |
| R2-2103815 | On the lack of PLMN identity check in case of anyCellSelected state related logging | Ericsson |
| R2-2103817 | On TimeUntilReconnection and ReconnectionCellID logging as part of RLF report | Ericsson |
| R2-2103818 | On releasing WLAN-BT-Sensor configurations upon returning from inactive | Ericsson |
| R2-2103820 | Report of email discussion [Post113-e][NR/R16 SON/MDT] Timestamp of event triggered MDT | Ericsson |
| R2-2103822 | ReconnectCellID in multi PLMN scenarios | Ericsson |
| R2-2103875 | Discussion on RLF reporting | Apple, Ericsson, MediaTek Inc. |
| R2-2103876 | Clarification on RA reporting | Apple |
| R2-2104002 | Discussion on the location reporting in inter-RAT measurement for immediate MDT | Huawei, HiSilicon |
| R2-2104003 | Discussion on the user consent for trace reporting | Huawei, HiSilicon |
| R2-2104198 | CR to 36331 on RLF report and logged MDT report | ZTE Corporation, Sanechips |
| R2-2104411 | Report of [AT113bis-e][607][POS] LPP proposals (CATT) | CATT |
| R2-2104435 | SON-MDT Changes agreed in RAN2#113-bis meeting | Ericsson, Huawei |
| R2-2104436 | SON-MDT Changes agreed in RAN2#113-bis meeting | Ericsson, Huawei |
| R2-2104599 | SON-MDT Changes agreed in RAN2#113-bis meeting | Ericsson, Huawei |
| R2-2104600 | SON-MDT Changes agreed in RAN2#113-bis meeting | Ericsson, Huawei |
| 7.2.1 | General and Stage-2 corrections | |
| R2-2102651 | LS on timing of neighbor cell RSS-based measurements (R4-2103657; contact: Qualcomm) | RAN4 |
| R2-2102653 | LS related to RSS based RSRQ for LTE-MTC (R4-2103728; contact: Huawei) | RAN4 |
| 7.2.2 | Connection to 5GC corrections | |
| R2-2103361 | Discussion on correction for paging DRX cycle determination | ZTE Corporation, Sanechips |
| R2-2104239 | draft LS to RAN3 to clarify paging DRX cycle | ZTE Corporation, Sanechips |
| R2-2104246 | Correction on paging DRX cycle | ZTE Corporation, Sanechips |
| R2-2104385 | Report of [AT113bis-e][401][eMTC R16] Paging DRX cycle (ZTE) | ZTE (email discussion rapporteur) |
| R2-2104388 | Report of [AT113bis-e][401][eMTC R16] Paging DRX cycle (ZTE) | ZTE (email discussion rapporteur) |
| 7.2.3 | Other corrections | |
| R2-2103012 | Draft reply LS on timing of neighbor cell RSS-based measurements | Qualcomm Incorporated |
| R2-2103013 | Whether to support RSRQ with RSS | Qualcomm Incorporated |
| R2-2103491 | RSRQ measurements when RSS is used | Huawei, HiSilicon |
| R2-2104182 | Consideration on LS related to RSS based RSRQ for eMTC | ZTE Corporation, Sanechips |
| R2-2104386 | [AT113bis-e][402][eMTC R16] Timing of neighbor cell RSS-based measurements (Qualcomm) | Qualcomm Incorporated |
| R2-2104387 | Offline 403 - RSRQ measurements when RSS is used | Huawei, HiSilicon |
| R2-2104389 | Draft reply LS on timing of neighbor cell RSS-based measurements | Qualcomm Incorporated |
| R2-2104390 | [draft] Reply LS related to RSS based RSRQ for LTE-MTC | Huawei |
| R2-2104391 | Reply LS on timing of neighbor cell RSS-based measurements | RAN2 |
| R2-2104392 | Reply LS related to RSS based RSRQ for LTE-MTC | RAN2 |
| 7.4 | LTE Other WIs | |
| R2-2102944 | RETX_COUNT upon expiry of t-PollRetransmit | Nokia, Nokia Shanghai Bell |
| R2-2103546 | Report on [Post113-e][206][LTE] Clarification to Fallback band combination definition (Nokia) | Nokia, Nokia Shanghai Bell |
| R2-2103547 | Clarification to Fallback band combination definition | Nokia, Nokia Shanghai Bell |
| R2-2104329 | Clarification to Fallback band combination definition | Nokia, Nokia Shanghai Bell |
| 7.5 | LTE Positioning | |
| R2-2104264 | Correction to LTE stage2 spec for MO-LR | Huawei, HiSilicon |
| R2-2104526 | Correction to LTE stage2 spec for MO-LR | Huawei, HiSilicon |
| 8.1.1 | Organizational, Requirements, Scope and Architecture | |
| R2-2102635 | Reply LS on 5MBS progress and issues to address (R3-211296; contact: Huawei) | RAN3 |
| R2-2102666 | Reply LS on 5MBS progress and issues to address (S2-2102077; contact: Huawei) | SA2 |
| R2-2102670 | Reply LS on 5MBS progress and issues to address (S3-211313; contact: Huawei) | SA3 |
| R2-2102716 | Discussion on Multicast in Idle and Inactive Mode | CATT, CBN |
| R2-2102838 | Discussion on SA2 LS and multicast session activation | Intel Corporation |
| R2-2102896 | RRC state control for MBS reception | OPPO |
| R2-2102938 | NR MBS operation in Idle/Inactive mode | Samsung |
| R2-2103118 | Considerations on the SA2 questions about session activation | vivo |
| R2-2103179 | NR Multicast group paging aspects | Qualcomm Inc |
| R2-2103180 | NR Multicast and Broadcast Radio Bearer Architecture aspects | Qualcomm Inc |
| R2-2103200 | Split MRB Protocol Architecture and Logical Channel Aggregation | Futurewei |
| R2-2103278 | MBS session activation and group paging | Nokia, Nokia Shanghai Bell |
| R2-2103372 | Further consideration of control plane aspects for NR MBS | Kyocera |
| R2-2103471 | draft LS about deployment scenarios of NR Broadcast | ZTE, Sanechips |
| R2-2103472 | NR Broadcast deployment scenarios | ZTE, Sanechips |
| R2-2103507 | Discussion on two delivery modes for NR MBS | CHENGDU TD TECH LTD. |
| R2-2103515 | Architecture aspects for NR MBS | Ericsson |
| R2-2103523 | Updated NR MBS workplan | Huawei, CMCC, HiSilicon |
| R2-2103650 | Layer-2 for MBS | Samsung |
| R2-2103728 | Discussion on SA2 Reply LS on 5G MBS | CMCC |
| R2-2103729 | Draft reply LS on Group Paging | CMCC |
| R2-2103775 | Multicast in Idle and Inactive | Ericsson, MediaTek, FirstNet, CBN |
| R2-2103905 | Discussion on group notification for multicast session activation | Huawei, HiSilicon |
| R2-2103906 | Reply LS on 5MBS progress and issues to address | Huawei, HiSilicon |
| R2-2103907 | Multicast session reception in RRC INACTIVE | Huawei, HiSilicon |
| R2-2104226 | Clarification on the PDCP-anchored MRB | Xiaomi Communications |
| R2-2104227 | MBS impacts on PDCP | Xiaomi Communications |
| R2-2104577 | [AT113bis-e][031][MBS17] MBS session activation (Nokia) | Rapporteur(Nokia) |
| R2-2104646 | Reply LS on 5MBS progress and issues to address | RAN2 |
| R2-2104655 | Reply LS on 5MBS progress and issues to address | RAN2 |
| 8.1.2.1 | Reliability | |
| R2-2102717 | Reliability Improvement for PTM Transmission | CATT |
| R2-2102782 | MBS UP architecture | MediaTek Inc. |
| R2-2102945 | MBS Reliability | Nokia, Nokia Shanghai Bell |
| R2-2103188 | NR Multicast PTM bearer RLC AM mode operation | Qualcomm Inc, FirstNet,UIC, Kyocera, AT&T |
| R2-2103201 | ARQ of PTM with Logical Channel Aggregation | Futurewei |
| R2-2103267 | HARQ modelling for supporting retransmission in MBS | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103374 | Consideration of possible solutions for L2 reliability in NR MBS | Kyocera |
| R2-2103413 | Issues on MBS reliability | Lenovo, Motorola Mobility |
| R2-2103450 | UE stay in RRC_CONNECTED when no MBS data ongoing | ASUSTeK |
| R2-2103473 | Consideration on MBS reliability guarantee | ZTE, Sanechips |
| R2-2103508 | Further discussion on reliability for RRC_CONNECTED state | CHENGDU TD TECH LTD. |
| R2-2103516 | Reliability and Dynamic Switch for MBS | Ericsson |
| R2-2103679 | Way forward on UP architecture for MBS | InterDigital Inc., ZTE, Sanechips, MediaTek Inc., Huawei, HiSilicon, Ericsson, LG Electronics Inc., Samsung Telecommunications, Fujitsu, Sharp, CATT, CBN, Spreadtrum Communications, Xiaomi Communications, Asia Pacific Telecom co. Ltd., OPPO, Lenovo, Motor |
| R2-2103871 | Consideration on the MBS transmission reliability | Apple |
| R2-2103949 | PTM Reliability Considerations | Convida Wireless |
| R2-2103963 | Way forward on UP architecture for MBS | InterDigital Inc., ZTE, Sanechips, MediaTek Inc., Huawei, HiSilicon, Ericsson, LG Electronics Inc., Samsung Telecommunications, Fujitsu, Sharp, CATT, CBN, Spreadtrum Communications, Xiaomi Communications, Asia Pacific Telecom co. Ltd., OPPO, Lenovo, Motor |
| R2-2104088 | Support of PDCP status reporting for PTM-PTP switching | SHARP Corporation |
| R2-2104150 | Comparison of L2 Reliability Solutions for MRB with dynamic PTM/PTP Switch | Futurewei, Qualcomm Inc, Intel |
| R2-2104161 | Discussion on reliability improvement and UL feedback in NR multicast | LG Electronics Inc. |
| R2-2104501 | Summary of A.I. 8.1.2.1 Reliability | LG Electronics Inc. |
| R2-2104588 | Email discussion report for [Post113-e][054][MBS17] PTP/PTM dynamic switch and MRB type change | Ericsson |
| 8.1.2.2 | Dynamic PTM PTP switch and service continuity | |
| R2-2102718 | Dynamic PTM/PTP Switch | CATT |
| R2-2102767 | Discussion on dynamic PTM and PTP switching | Shanghai Jiao Tong University |
| R2-2102783 | Dynamic Switch for NR MBS | MediaTek Inc. |
| R2-2103119 | Dynamic PTM PTP switch for RRC Connected UE | vivo |
| R2-2103163 | PTP_PTM dynamic switch | NEC |
| R2-2103202 | Service Continuity during Dynamic PTM/PTP Switch with Logical Channel Aggregation | Futurewei |
| R2-2103255 | Discussion on dynamic PTM PTP switching | Spreadtrum Communications |
| R2-2103358 | Dynamic PTM PTP switching | LG Electronics Inc. |
| R2-2103373 | Consideration of dynamic PTM - PTP switching with service continuity for NR MBS | Kyocera |
| R2-2103414 | MBS dynamic switch between PTP and PTM with service continuity | Lenovo, Motorola Mobility |
| R2-2103474 | Mode switching signaling of NR MBS | ZTE, Sanechips |
| R2-2103512 | Procedure for dynamic PTM/PTP switch | CHENGDU TD TECH LTD. |
| R2-2103518 | Email discussion report [Post113-e][054]PTP/PTM dynamic switch and MRB type change | Ericsson (Rapporteur) |
| R2-2103524 | PTP/PTM dynamic switch and MRB initialization | Huawei, CBN, HiSilicon |
| R2-2103543 | MRB and DRB configuration | Sony Europe B.V. |
| R2-2103649 | Discussion on MRB | Samsung |
| R2-2103680 | PTM/PTP mode switching | InterDigital |
| R2-2103872 | MBS PTP/PTM switching | Apple |
| R2-2104118 | Dynamic switch between PTM and PTP for service continuity | Intel Corporation |
| R2-2104207 | Support of dynamic switch between PTP and PTM | SHARP Corporation |
| 8.1.2.4 | Other | |
| R2-2102719 | Discussion on Group Scheduling | CATT |
| R2-2102765 | Discussion on deactivation of MBS reception | Shanghai Jiao Tong University |
| R2-2102766 | Consideration on Group Scheduling for NR MBS | Shanghai Jiao Tong University |
| R2-2102784 | RAN2 aspects of Group Scheduling for NR MBS | MediaTek Inc. |
| R2-2102785 | L1 HARQ operation for PTM transmission | MediaTek Inc. |
| R2-2102839 | MBS MAC Layer and Group Scheduling Aspects | Intel Corporation |
| R2-2102895 | Discussion on group based scheduling for MBS | OPPO |
| R2-2102934 | On Group Scheduling and Multiplexing Aspects | Samsung |
| R2-2102937 | On MBS DRX, Data-Inactivity & BWP aspects | Samsung |
| R2-2102946 | Miscellaneous Aspects of MBS Provisioning | Nokia, Nokia Shanghai Bell |
| R2-2103120 | Updated summary for MBS Group Scheduling | vivo |
| R2-2103121 | Group Scheduling for MBS | vivo |
| R2-2103254 | Discussion on MBS session activation/deactivation and UAC | Spreadtrum Communications |
| R2-2103359 | MBS configuration for RRC_CONNECTED | LG Electronics Inc. |
| R2-2103416 | MBS Group Scheduling Aspects | Lenovo, Motorola Mobility |
| R2-2103475 | Discussion on Group scheduling for NR MBS | ZTE, Sanechips |
| R2-2103517 | Aspects of Group Scheduling | Ericsson |
| R2-2103525 | RAN2 aspects of group scheduling | Huawei, CBN, HiSilicon |
| R2-2103703 | Discussion on group scheduling for MBS | CMCC |
| R2-2103873 | MBS reception in CONNECTED state | Apple |
| R2-2104162 | Discussion on RAN2 aspects of group scheduling | LG Electronics Inc. |
| R2-2104228 | Discussion on group scheduling | Xiaomi Communications |
| R2-2104494 | Updated summary for MBS Group Scheduling | vivo |
| 8.1.3 | Idle and Inactive mode UEs | |
| R2-2102720 | Further Discussion on Delivery Mode 2 | CATT, CBN |
| R2-2102893 | Discussion on beam sweeping transmission for delivery mode 2 | OPPO |
| R2-2102894 | Discussion on MBS interesting indication and service continuity for delivery mode 2 | OPPO |
| R2-2103122 | MBS in Idle and Inactive Mode | vivo |
| R2-2103152 | Configuration and scheduling in MBS delivery mode 2 | Futurewei |
| R2-2103167 | Discussion on Beam Sweeping Configuration for Flexible MBS Control Plane Scheduling | TCL Communication Ltd. |
| R2-2103178 | NR MBS control signalling aspects for UEs in different RRC states | Qualcomm Inc |
| R2-2103256 | Discussion issues on delivery mode2 | Spreadtrum Communications |
| R2-2103277 | MBS Idle | Nokia, Nokia Shanghai Bell |
| R2-2103360 | MBS in IDLEINACTIVE | LG Electronics Inc. |
| R2-2103415 | Discussion on MBS delivery modes | Lenovo, Motorola Mobility |
| R2-2103476 | Idle and Inactive mode UEs support of NR MBS | ZTE, Sanechips |
| R2-2103513 | Further discussion on delivery mode 2 for NR MBS | CHENGDU TD TECH LTD. |
| R2-2103670 | Considerations on measurements for NR MBS in idle/inactive | Lenovo, Motorola Mobility |
| R2-2103704 | Discussion on delivery mode 2 remaining issues | CMCC |
| R2-2103705 | Discussion on delivery mode 2 transmission | CMCC |
| R2-2103706 | LS on delivery mode 2 transmission | CMCC |
| R2-2103776 | Open issues for UEs in idle or inactive mode | Ericsson |
| R2-2103874 | MBS reception in IDLE/INACTIVE state | Apple |
| R2-2103908 | Service continuity aspects of delivery mode 2 | Huawei, HiSilicon, CBN |
| R2-2103909 | Report of e-mail discussion: [Post113-e][053][MBS17] MCCH scheduling and MCCH change notification (Huawei) | Huawei, HiSilicon |
| R2-2103946 | On NR multicast and broadcast for RRC_IDLE/RRC_INACTIVE UEs | Convida Wireless |
| R2-2103947 | NR MBS Configuration Information | Convida Wireless |
| R2-2104089 | L2 architecture for delivery mode 2 | SHARP Corporation |
| R2-2104119 | MBS support for delivery mode 2 | Intel Corporation |
| R2-2104229 | Remaining issues of MCCH and MCCH change notification | Xiaomi Communications |
| R2-2104230 | Service continuity for delivery mode 2 | Xiaomi Communications |
| R2-2104284 | Performance improvement for delivery mode 2 | CHENGDU TD TECH LTD. |
| R2-2104509 | Report of e-mail discussion: [Post113-e][053][MBS17] MCCH scheduling and MCCH change notification (Huawei) | Huawei, HiSilicon |
| R2-2104629 | Report of offline discussion: [AT113bis-e][032][MBS17] MCCH scheduling and Change notification (Huawei) | Huawei, HiSilicon |
| R2-2104630 | [DRAFT] LS on broadcast session delivery and MCCH design | Huawei |
| R2-2104639 | LS on broadcast session delivery and MCCH design | RAN2 |
| 8.2.1 | Organizational, Requirements and Scope | |
| R2-2102642 | Reply LS on Conditional PSCell Addition/Change agreements (R3-211338; contact: Huawei) | RAN3 |
| R2-2103037 | TS 37.340 CR for SCG deactivation and activation | ZTE Corporation, Sanechips |
| R2-2103980 | Introduction of further MRDC enhancements | Huawei, HiSilicon |
| R2-2104340 | TS 37.340 CR for SCG deactivation and activation | ZTE Corporation, Sanechips |
| R2-2104352 | Reply LS on Conditional PSCell Addition/Change agreements | RAN2 |
| 8.2.2 | Efficient activation / deactivation mechanism for one SCG and SCells | |
| R2-2103982 | SCG activation and deactivation procedure | Huawei, HiSilicon |
| 8.2.2.1 | Deactivation of SCG | |
| R2-2102898 | Open issues for SCG deactivation procedure | OPPO |
| R2-2103106 | Discussion on Deactivation of SCG | CATT |
| R2-2103274 | Deactivation of SCG | Nokia, Nokia Shanghai Bell |
| R2-2103397 | Discussion on SCG deactivation | Lenovo, Motorola Mobility |
| R2-2103503 | Issues on SCG deactivation procedure | NEC |
| R2-2103681 | Activation and Deactivation of SCG | InterDigital |
| R2-2103722 | Discussions on deactivation of SCG | CMCC |
| R2-2103807 | SCG deactivation procedures | Ericsson |
| R2-2103890 | Deactivation of SCG | Qualcomm Incorporated |
| R2-2103913 | UE assistance information use case for SCG deactivation | Convida Wireless |
| R2-2103931 | SCG activation/ deactivation procedure | Samsung Telecommunications |
| R2-2103977 | SCG deactivation | Huawei, HiSilicon |
| R2-2104159 | NW-triggered SCG activation and deactivation | MediaTek Inc. |
| R2-2104237 | Further consideration on SCG activation and deactivation | NTT DOCOMO INC. |
| R2-2104315 | Summary of AI 8.2.2.1: Deactivation of SCG | Huawei |
| 8.2.2.2 | UE measurements and reporting in deactivated SCG | |
| R2-2102749 | Considerations on RLM during SCG deactivation | KDDI Corporation |
| R2-2102872 | UE behavior when SCG is deactivated | vivo |
| R2-2102897 | UE measurements and reporting in deactivated SCG | OPPO |
| R2-2103036 | Discussion on UE behaviour when SCG is deactivated | ZTE Corporation, Sanechips |
| R2-2103107 | UE Behavior in Deactivated SCG | CATT |
| R2-2103275 | Measurements for deactivated SCG | Nokia, Nokia Shanghai Bell |
| R2-2103294 | DC power sharing for deactivated SCG | Samsung |
| R2-2103398 | UE behavior when SCG is deactivated | Lenovo, Motorola Mobility |
| R2-2103505 | Further considerations on SCG deactivation | NEC |
| R2-2103569 | UE Measurement Aspects in SCG Deactivation | LG Electronics |
| R2-2103682 | Measurements and maintenance of UL synch with a deactivated SCG | InterDigital |
| R2-2103740 | Discussion on UE behavior in deactivated SCG | China Telecommunications |
| R2-2103777 | Mobility for deactivated SCG | NTT DOCOMO, INC. |
| R2-2103808 | UE measurements and reporting in deactivated SCG | Ericsson |
| R2-2103885 | TA Maintenance and other UE actions in SCG deactivated state | Apple |
| R2-2103893 | UE measurements and reporting in deactivated SCG | Qualcomm Incorporated |
| R2-2103978 | UE behaviour in deactivated SCG | Huawei, HiSilicon |
| R2-2104124 | Discussion for UE behaviour in deactivated SCG | SHARP Corporation |
| R2-2104160 | UE behavior during SCG deactivation | MediaTek Inc. |
| R2-2104316 | Summary of AI 8.2.2.2: UE measurements and reporting in deactivated SCG | OPPO |
| R2-2104334 | Summary of [AT113bis-e][240][DCCA] RRM relaxations for deactivated SCG (OPPO) | OPPO |
| R2-2104523 | Offline of RRM relax and DL fine Sync for SCG deactivation (OPPO) | OPPO |
| 8.2.2.3 | Activation of deactivated SCG | |
| R2-2102873 | Activation of deactivated SCG | vivo |
| R2-2102899 | Open issues for activation of deactivated SCG | OPPO |
| R2-2103035 | Activation and deactivation of SCG | ZTE Corporation, Sanechips |
| R2-2103108 | Considerations on Activation of Deactivated SCG | CATT |
| R2-2103153 | Access handling with TAT in SCG fast activation | Futurewei |
| R2-2103154 | Measurement report and RLM handling for deactivated SCG | Futurewei |
| R2-2103251 | Discussion on UE behavior when SCG is deactivated | Spreadtrum Communications |
| R2-2103276 | Activation of SCG | Nokia, Nokia Shanghai Bell |
| R2-2103399 | Discussion on SCG activation | Lenovo, Motorola Mobility |
| R2-2103504 | Issues on SCG activation procedure | NEC |
| R2-2103570 | Acrivation and Deactivation on SCG | LG Electronics |
| R2-2103723 | Discussions on activation of deactivated SCG | CMCC |
| R2-2103809 | SCG activation procedures | Ericsson |
| R2-2103886 | UE initiation of SCG re-activation request | Apple |
| R2-2103895 | Activation of deactivated SCG | Qualcomm Incorporated |
| R2-2103979 | SCG activation | Huawei, HiSilicon |
| R2-2104164 | UE behaviour upon SCG activation | MediaTek Inc. |
| R2-2104170 | Discussion on SCG activation | SHARP Corporation |
| R2-2104231 | Considerations on reactivating SCG | Intel Corporation |
| R2-2104317 | Summary of AI 8.2.2.3: Activation of deactivated SCG | ZTE Corporation |
| 8.2.3.1 | CPAC procedures and signalling flows | |
| R2-2102861 | Discussion on the configuration of CPAC | vivo |
| R2-2103109 | Summary of [Post113-e][234][eDCCA] CPAC procedures (CATT) | CATT |
| R2-2103155 | Discussion on issues with SN initiated CPC | Futurewei |
| R2-2103158 | Remaining issues for SN initiated inter-SN CPC | China Telecommunication |
| R2-2103354 | Discussion on procedures in CPAC and conventional PSCell change | ITRI |
| R2-2103883 | Details in conditional PSCell change and addition | Apple |
| R2-2103932 | CPAC stage 2 flow, progressing remaining issues | Samsung Telecommunications |
| R2-2103986 | Discussion on the inter-node message design (RAN3 LS) | Huawei Technologies France |
| R2-2104073 | Further consideration on CPAC | ZTE Corporation, Sanechips |
| 8.2.3.2 | CPAC coexistence with CHO and CPAC failure handling | |
| R2-2102950 | Failure handling of Conditional PSCell Addition | DENSO CORPORATION |
| R2-2103355 | Discussion on SCG RLF handling in case CPC is configured | ITRI |
| R2-2103571 | Coexistence and other issues in CPAC | LG Electronics |
| R2-2103683 | Coexistence of CHO and CPC | InterDigital, Nokia |
| R2-2103721 | Combination of CPAC and CHO | CMCC |
| 8.2.3.3 | Other CPAC aspects | |
| R2-2103253 | CPC configuration number restriction | Spreadtrum Communications |
| 8.3.1 | Organizational, Requirements and Scope | |
| R2-2102664 | LS on System support for Multi-USIM devices (S2-2102039; contact: Intel) | SA2 |
| R2-2103343 | Running CR to 36300 for Multi-USIM devices support | vivo |
| R2-2103344 | Running CR to 38300 for Multi-USIM devices support | vivo |
| 8.3.2 | Paging collision avoidance | |
| R2-2102792 | Paging Collision Avoidance | OPPO |
| R2-2102939 | Considerations for Paging Collision Avoidance Solution | Samsung |
| R2-2102948 | Further Consideration on Paging Collision Avoidance | CATT |
| R2-2103160 | Paging collision solution of Multi-SIM | China Telecommunication |
| R2-2103185 | RAN Impacts for paging collision avoidance solutions for Multi-SIM | Nokia, Nokia Shanghai Bells |
| R2-2103193 | 5G-S-TMSI re-assignment is enough for paging collision avoidance in 5GS | Intel Corporation |
| R2-2103225 | Options for paging collision avoidance | Qualcomm Incorporated |
| R2-2103345 | Paging Collision Solution for 5GS | vivo |
| R2-2103451 | UE indication of paging collision for Multi-SIM | ASUSTeK |
| R2-2103480 | Paging Collision Avoidance Open Issues | Huawei, HiSilicon |
| R2-2103544 | Discussion on paging collision avoidance in Multi-SIM, and proposal for response to SA2. | Sony Europe B.V. |
| R2-2103572 | Considerations on Paging Collision | LG Electronics |
| R2-2103677 | Solutions for Paging Collision Avoidance for Multi-SIM | Charter Communications, Inc |
| R2-2103743 | Definition and solution for paging collision, RRC Inactive, SI change | Lenovo, Motorola Mobility |
| R2-2103757 | Paging collision avoidance | Ericsson |
| R2-2103830 | MUSIM Page Collision Avoidance | Apple |
| R2-2104151 | Paging collision avoidance for MUSIM device | MediaTek Inc. |
| R2-2104168 | Discussion of the paging collision problem in 5GS | Xiaomi Communications |
| R2-2104242 | Consideration on the Paging Collision | ZTE Corporation, Sanechips |
| R2-2104318 | Summary of AI 8.3.2: Paging collision avoidance | Ericsson |
| 8.3.3 | UE notification on network switching for multi-SIM | |
| R2-2102793 | UE Notification on Network Switching for Multi-SIM | OPPO |
| R2-2102811 | Analysis on various scenarios of UE switching | China Telecommunications |
| R2-2102940 | Signalling design on short time switching procedure | DENSO CORPORATION |
| R2-2102949 | Further Consideration on Network Switching | CATT |
| R2-2103017 | Discussions on various ways to support various of leave scenarios and procedures for Multi-SIM UEs | CableLabs |
| R2-2103184 | Switching notification for basic scenario for Multi-SIM | Nokia, Nokia Shanghai Bells |
| R2-2103194 | Multi-SIM busy indication signaling for INACTIVE | Intel Corporation |
| R2-2103224 | Network switching mechanisms for Multi-SIM | Qualcomm Incorporated |
| R2-2103247 | Discussion on the transmission of busy indication | Spreadtrum Communications |
| R2-2103300 | UE notification procedure for short time switching | NEC |
| R2-2103346 | Handling leftovers from email discussion on Switching Notification | vivo |
| R2-2103347 | Discussion on Switching Notification | vivo |
| R2-2103417 | Switching notification and busy indication | Lenovo, Motorola Mobility |
| R2-2103452 | MUSIM Release Assistance Info for network switching | ASUSTeK |
| R2-2103545 | Discussion on Busy Indication and Leaving in Multi-SIM | Sony Europe B.V. |
| R2-2103573 | Considerations on SIM Swithcing | LG Electronics |
| R2-2103588 | On coordinated switch from NW for MUSIM device | Huawei, HiSilicon |
| R2-2103678 | Network Switching Solutions for Multi-SIM | Charter Communications, Inc |
| R2-2103756 | Graceful leaving for a Multi-USIM device | Ericsson |
| R2-2103831 | MUSIM Network Switching | Apple |
| R2-2103832 | MUSIM Band Conflict and RRC Processing Delay Requirements | Apple |
| R2-2103957 | Procedures for MSIM UE notification on network switching | Futurewei Technologies |
| R2-2104154 | Network switching behavior for MUSIM device | MediaTek Inc. |
| R2-2104169 | Discussion of the UE notification on network switching for multi-SIM | Xiaomi Communications |
| R2-2104174 | Open issues on network switching for Multi-USIM devices | Samsung Electronics Co., Ltd |
| R2-2104211 | RNAU Handling in MUSIM | SHARP Corporation |
| R2-2104215 | Switching Notification for leaving RRC_CONNECTED | SHARP Corporation |
| R2-2104243 | Consideration on the Switching Notification Procedure | ZTE Corporation, Sanechips |
| R2-2104244 | Consideration on the Busy Indication | ZTE Corporation, Sanechips |
| R2-2104319 | Summary of AI 8.3.3: UE notification on network switching for multi-SIM | Samsung |
| R2-2104332 | Summary of [AT113bis-e][231][MUSIM] Impacts of NAS-based busy indication (RAN2 VC) | Nokia (RAN2 VC) |
| R2-2104333 | Draft LS on NAS-based busy indication | Nokia (RAN2 VC) |
| R2-2104351 | [DRAFT] LS on NAS-based busy indication | vivo |
| R2-2104354 | LS on NAS-based busy indication | RAN2 |
| 8.3.4 | Paging with service indication | |
| R2-2102794 | Paging with Service Indication | OPPO |
| R2-2102913 | Discussion on support of paging cause for multi-USIM devices | Samsung Electronics Co., Ltd |
| R2-2103186 | Further analysis on Service type indication in paging and signalling mechanism for BUSY indication | Nokia, Nokia Shanghai Bells |
| R2-2103195 | Support for Multi-SIM paging cause from SA2 LS | Intel Corporation |
| R2-2103226 | Paging Cause and Busy Indication | Qualcomm Incorporated |
| R2-2103246 | Supporting of Paging Cause Solution detection | Spreadtrum Communications |
| R2-2103248 | Discussion on the transmission of paging cause | Spreadtrum Communications |
| R2-2103304 | Introduction of paging cause | China Telecommunications |
| R2-2103348 | Introduction of Paging Cause | vivo |
| R2-2103483 | Discussion on the paging with service indication | Huawei, HiSilicon |
| R2-2103574 | Support of Paging Cause | LG Electronics |
| R2-2103758 | Introduction of a Paging cause indication | Ericsson |
| R2-2103958 | Discussion on paging service indication for MUSIM | Futurewei Technologies |
| R2-2104158 | Paging with service indication | MediaTek Inc. |
| R2-2104171 | Discussion of the paging cause support for MUSIM | Xiaomi Communications |
| R2-2104320 | Summary of AI 8.3.4: Paging with service indication | vivo |
| R2-2104331 | Summary of [AT113bis-e][230][MUSIM] Reply LS to SA2 on paging cause (Intel) | Intel |
| 8.4.1 | Organizational Requirements and Scope | |
| R2-2102608 | Reply LS on inter-donor topology redundancy (R1-2101880; contact: Samsung) | RAN1 |
| R2-2102636 | LS on inter-donor-DU re-routing (R3-211298; contact: Huawei) | RAN3 |
| R2-2102637 | LS on DAPS-like solution for IAB (R3-211326; contact: Qualcomm) | RAN3 |
| R2-2102638 | LS on inter-donor topology redundancy (R3-211331; contact: Samsung) | RAN3 |
| R2-2103080 | Updated Rel-17 IAB Workplan | Qualcomm Incorporated, Samsung (WI rapporteurs) |
| R2-2103842 | On UE L2 re-ordering buffer size concerns in IAB Networks | Apple |
| R2-2104117 | Draft Reply LS on inter-donor-DU re-routing | Huawei, HiSilicon |
| 8.4.2 | Enhancements to improve topology-wide fairness multi-hop latency and congestion mitigation | |
| R2-2102727 | Consideration on topology-wide fairness, multi-hop latency and congestion mitigation | CATT |
| R2-2102833 | IAB topology-wide fairness and latency enhancement | Intel Corporation |
| R2-2103081 | Fairness support in IAB topology | Qualcomm Incorporated |
| R2-2103082 | Enhancements to improve IAB multi-hop latency | Qualcomm Incorporated |
| R2-2103138 | Discussion on topology-wide fairness multi-hop latency and congestion mitigation | ZTE, Sanechips |
| R2-2103283 | Discussion on the fairness improvement, multi-hop latency and congestion mitigation | Fujitsu |
| R2-2103349 | Discussion on miscellaneous issues in eIAB | vivo |
| R2-2103353 | An elaboration of required PDB for multi-hop latency | ITRI |
| R2-2103370 | Possible solutions for topology-wide fairness, multi-hop latency and congestion mitigation in eIAB | Kyocera |
| R2-2103418 | Further consideration on identified issues for fairness, latency and congestion | LG Electronics Inc. |
| R2-2103499 | Fairness, latency and congestion – solutions to identified issues | Samsung Electronics GmbH |
| R2-2103526 | Fairness, latency, congestion | Nokia, Nokia Shanghai Bell |
| R2-2103562 | Solutions to improve topology-wide fairness, latency and congestion mitigation | Sony Europe B.V. |
| R2-2103684 | Enforcing multi-hop latency in multi-hop IAB | InterDigital |
| R2-2103685 | Fairness and congestion mitigation in multi-hop IAB | InterDigital |
| R2-2103840 | Solutions to ensure fairness, latency bounds and mitigation of congestion impacts in eIAB Networks | Apple |
| R2-2103940 | On Topology-wide Fairness, Multi-hop Latency, and Congestion in IAB Network | Ericsson |
| R2-2103955 | Multi-hop scheduling and local routing enhancements for IAB | AT&T |
| R2-2103987 | Rel. 17 IAB enhancements for fairness, multi-hop latency reduction, and congestion mitigation | Futurewei Technologies |
| R2-2104123 | Enhancements for topology-wide fairness, multi-hop latency and congestion mitigation | Huawei, HiSilicon |
| R2-2104491 | Summary of Rel-17 IAB contributions on fairness, latency and congestion | Qualcomm (WI rapporteur) |
| R2-2104535 | Summary of Rel-17 IAB contributions on fairness, latency and congestion | Qualcomm (WI rapporteur) |
| 8.4.3 | Topology adaptation enhancements | |
| R2-2102728 | Mobility of Descendant IAB-Nodes | CATT |
| R2-2102729 | RLF Indication and Local Rerouting | CATT |
| R2-2102730 | Report from email discussion [Post113-e][057][IAB17] CHO and DAPS for IAB (CATT) | CATT |
| R2-2102834 | Intra-donor CHO, local rerouting and RLF indication enhancement | Intel Corporation |
| R2-2102835 | Inter-donor topology adaptation and topology redundancy | Intel Corporation |
| R2-2102844 | Discussion on DAPS-like solution for IAB | Intel Corporation |
| R2-2102931 | Discussion on BH RLF | LG Electronics France |
| R2-2102933 | Discussion on CHO and DAPS-like Solution | LG Electronics France |
| R2-2103083 | Report [Post113-e][058][IAB17] Inter-donor topology adaptation | Qualcomm Incorporated |
| R2-2103084 | Topology adaptation enhancements | Qualcomm Incorporated |
| R2-2103128 | Discussion on topology adaptation enhancements | Samsung Electronics Nordic AB |
| R2-2103139 | Discussion on RLF indication and local re-routing | ZTE, Sanechips |
| R2-2103140 | Discussion on CP-UP separation and topology redundancy | ZTE, Sanechips |
| R2-2103141 | Discussion on supporting CHO and DAPS in IAB | ZTE, Sanechips |
| R2-2103161 | DAPS like HO for IAB | NEC |
| R2-2103162 | CHO for IAB | NEC |
| R2-2103284 | Topology adaptation enhancements | Fujitsu |
| R2-2103285 | Discussion on the inter-donor topology redundancy | Fujitsu |
| R2-2103286 | Re-routing for UL packet loss reduction | Fujitsu |
| R2-2103350 | On DAPS like operation of eIAB | vivo |
| R2-2103351 | On intra-donor CHO of eIAB | vivo |
| R2-2103352 | On BAP routing of intra-CU local rerouting and inter-donor DC | vivo |
| R2-2103371 | Details of topology adaptation enhancements for eIAB | Kyocera |
| R2-2103391 | CHO in IAB system | Lenovo, Motorola Mobility |
| R2-2103392 | Discussion on DAPS for IAB network | Lenovo, Motorola Mobility |
| R2-2103393 | Discussion on IAB packet rerouting | Lenovo, Motorola Mobility |
| R2-2103419 | Discussion on inter-donor DU local re-routing and further details on local re-routing | LG Electronics Inc. |
| R2-2103453 | Handling Type-2 & Type-3 RLF indication | ASUSTeK |
| R2-2103477 | New triggers for local rerouting | Samsung Electronics GmbH |
| R2-2103484 | Inter-donor-DU rerouting | Samsung Electronics GmbH |
| R2-2103559 | Multi-parent options | Nokia, Nokia Shanghai Bell |
| R2-2103560 | Re-routing enhancements and RLF indications in IAB | Nokia, Nokia Shanghai Bell |
| R2-2103561 | Inter-donor-DU rerouting for IAB | Nokia, Nokia Shanghai Bell |
| R2-2103563 | Topology adaptation enhancements in IAB | Sony Europe B.V. |
| R2-2103565 | DAPS-like solution in IAB | Sony Europe B.V. |
| R2-2103686 | CHO triggering In IAB | InterDigital |
| R2-2103687 | On DAPS support in IAB | InterDigital |
| R2-2103841 | Discussion on topology adaptation enhancements in eIAB Networks | Apple |
| R2-2103938 | On IAB Inter-donor Topology Adaptation | Ericsson |
| R2-2103939 | On CHO and DAPS for IAB | Ericsson |
| R2-2103941 | CP/UP Separation in IAB Network | Ericsson |
| R2-2104120 | Inter-donor-DU rerouting and local rerouting enhancement | Huawei, HiSilicon |
| R2-2104121 | Inter-donor routing for R17-IAB | Huawei, HiSilicon |
| R2-2104122 | F1 over NR access link, CHO and DAPS | Huawei, HiSilicon |
| R2-2104152 | RAN2 impacts of Rel.17 IAB topology adaptation enhancements | Futurewei Technologies |
| 8.5.1 | Organizational | |
| R2-2102631 | LS on gNB-based propagation delay compensation (R3-211136; contact: Nokia) | RAN3 |
| 8.5.3 | Uplink enhancements for URLLC in unlicensed controlled environments | |
| R2-2102685 | CG Harmonization for Unlicensed Controlled Environment | Qualcomm Incorporated |
| R2-2102725 | URLLC in UCE | CATT |
| R2-2102992 | HARQ Process Prioritization of Configured Grant for IIoT in NR-U | Nokia, Nokia Shanghai Bell |
| R2-2103059 | Remaining issues about uplink enhancements for URLLC in UCE | Huawei, HiSilicon |
| R2-2103072 | Uplink enhancements for URLLC in unlicensed controlled environments | Intel Corporation |
| R2-2103126 | Issue of Prioritizing Initial Transmission over Retransmission on a CG | vivo |
| R2-2103211 | Consideration on URLLC over NRU | OPPO |
| R2-2103297 | Enhancements for URLLC in unlicensed controlled environments | Lenovo, Morotola Mobility |
| R2-2103428 | Harmonizing UL CG enhancements in NR-U and URLLC | Ericsson |
| R2-2103441 | Further Consideration on the UL transmission in UCE | ZTE Corporation, Sanechips |
| R2-2103492 | CG Harmonization for NR-U and IIoT/URLLC in Unlicensed Controlled Environments | III |
| R2-2103566 | Prioritization of UL transmissions in unlicensed URLLC | Sony Europe B.V. |
| R2-2103648 | CG Harmonization for UCE | Samsung |
| R2-2103688 | Discussion on the remaining issue for uplink enhancements for URLLC in UCE | CMCC |
| R2-2103797 | IIoT operation in unlicensed controlled environments | InterDigital |
| R2-2104103 | Further details on harmonization | LG Electronics UK |
| R2-2104224 | Remaining issues of CG harmonization | Xiaomi Communications |
| R2-2104288 | Remaining issues of CG harmonization | Xiaomi Communications |
| 8.5.4 | RAN enhancements based on new QoS | |
| R2-2102686 | RAN Enhancement to support new QoS | Qualcomm Incorporated |
| R2-2102726 | Handling of Survival Time | CATT |
| R2-2102993 | RAN Enhancement for New QoS Parameters | Nokia, Nokia Shanghai Bell |
| R2-2103060 | RAN enhancements based on new QoS related parameters | Huawei, HiSilicon |
| R2-2103125 | Discussion on RAN enhancement to support survival time | vivo |
| R2-2103196 | Topics on new QoS handling | Fujitsu |
| R2-2103212 | RAN enhancement based on new QoS | OPPO |
| R2-2103329 | Further considerations on new QoS | ZTE Corporation, Sanechips, China Southern Power Grid Co., Ltd |
| R2-2103420 | Discussion on RAN enhancements based on Survival Time | III |
| R2-2103429 | RAN enhancements based on new QoS related parameters | Ericsson |
| R2-2103432 | Entering and operating in the Survival Time state | Samsung Electronics GmbH |
| R2-2103689 | Discussion on the RAN support for new QoS parameters | CMCC |
| R2-2103735 | RAN2 Enhancements for Support of QoS Parameters | Intel Corporation |
| R2-2103798 | Enhancements based on new QoS requirements | InterDigital |
| R2-2103896 | Discussion on entering and exiting survival time state | Futurewei Technologies |
| R2-2104097 | View on survival time mechanisms | LG Electronics UK |
| R2-2104225 | Clarification on the survival time | Xiaomi Communications |
| R2-2104265 | RAN enhancements based on new QoS | TCL Communication Ltd. |
| 8.6.1 | Organizational | |
| R2-2102620 | Reply LS on physical layer aspects of small data transmission (R1-2102125; contact: ZTE) | RAN1 |
| R2-2102634 | Reply LS on small data transmission (R3-211280; contact: Ericsson) | RAN3 |
| R2-2102707 | Report from email discussion [POST113-e][501][SDT] Selection criteria and overall Procedure | Samsung Electronics Co., Ltd |
| R2-2103022 | Summary of General and other control plane open issues for SDT (email: [Post 113-e][502]) | Rapporteur (ZTE) |
| R2-2103527 | Stage-2 running CR Introduction of SDT | Nokia, Nokia Shanghai Bell |
| R2-2103897 | DRAFT Reply LS on small data transmission | Ericsson |
| R2-2104398 | DRAFT Reply LS on small data transmission | Ericsson |
| R2-2104400 | Reply LS on small data transmission | RAN2 |
| R2-2104402 | Reply LS on small data transmission | RAN2 |
| R2-2104490 | DRAFT Reply LS on physical layer aspects of small data transmission (Reply to R2-2102620) | ZTE Corporation |
| 8.6.2 | User plane common aspects | |
| R2-2102708 | User Plane Common Aspects of RACH and CG based SDT | Samsung Electronics Co., Ltd |
| R2-2102750 | Discussion on user plane issues of SDT | OPPO |
| R2-2102755 | Discussion on User Plane Aspect of Small Data Transmission | vivo |
| R2-2102840 | User plane aspects for SDT | Intel Corporation |
| R2-2103018 | User plane open issues for SDT | ZTE Corporation, Sanechips |
| R2-2103102 | Analysis on UP common aspects of SDT | CATT |
| R2-2103197 | Support of CA and PDCP CA duplication | Fujitsu |
| R2-2103319 | The UP common issues for small data transmissions | Lenovo, Motorola Mobility |
| R2-2103430 | Discussion on user plane common aspects of NR small data transmission | Qualcomm Incorporated |
| R2-2103444 | Discussion on data volume threshold for small data transmission | PANASONIC R&D Center Germany |
| R2-2103454 | Avoid triggering RA during subsequent SDT | ASUSTeK |
| R2-2103521 | Common aspects for SDT | Ericsson |
| R2-2103528 | User Plane common aspects | Nokia, Nokia Shanghai Bell |
| R2-2103531 | User plane common aspects for SDT | Huawei, HiSilicon |
| R2-2103583 | Some aspects of User Plane for SDT in NR | Sony Europe B.V. |
| R2-2103672 | Discussion on small data transmission | Google Inc. |
| R2-2103674 | Discussion on beam operations for small data transmission | Google Inc. |
| R2-2103714 | Remaining issues on transmission type selection and overall procedure | CMCC |
| R2-2103870 | User plane aspects on the SDT procedure | Apple |
| R2-2103990 | Consideration on overall SDT procedure and criteria | LG Electronics Inc. |
| R2-2104206 | On the overall and detailed procedure of SDT | China Telecommunications |
| R2-2104220 | Discussion on data volume calculation | Xiaomi Communications |
| R2-2104263 | Discussion on Small Data Transmission | TCL Communication Ltd. |
| R2-2104395 | Report of [AT113bis-e][501][SDT] UP SDT open issues | LG Electronics (Rapporteur) |
| 8.6.3 | Control plane common aspects | |
| R2-2102709 | Control Plane Common Aspects of RACH and CG based SDT | Samsung Electronics Co., Ltd |
| R2-2102751 | Discussion on control plane issues of SDT | OPPO |
| R2-2102756 | Discussion on RRC-Controlled Small Data Transmission | vivo |
| R2-2102841 | Signalling and NAS-AS interaction for SDT | Intel Corporation |
| R2-2102842 | Fallback and failure handling for SDT | Intel Corporation |
| R2-2102900 | New timers for SDT failure detection | Langbo |
| R2-2102991 | Handling of non-SDT traffic arrival | PANASONIC R&D Center Germany |
| R2-2103019 | Control plane aspects of SDT | ZTE Corporation, Sanechips |
| R2-2103103 | Considerations on Some Common Control Plane Issues | CATT |
| R2-2103151 | Handling of non-SDT data arrival | Potevio Company Limited |
| R2-2103198 | RAN paging reception and response during SDT | Fujitsu |
| R2-2103257 | Handling of non-SDT data during SDT | ETRI |
| R2-2103299 | Discuss on solutions for arriving of non-SDT data during SDT | NEC |
| R2-2103405 | Consideration on CP issues for small data transmission | Lenovo, Motorola Mobility |
| R2-2103431 | Discussion on control plane common aspects of NR small data transmission | Qualcomm Incorporated |
| R2-2103455 | Beam management in SDT | ASUSTeK |
| R2-2103497 | SDT control plane aspects | Nokia, Nokia Shanghai Bell |
| R2-2103522 | CP aspects for SDT | Ericsson |
| R2-2103568 | Discussion on subsequent SDT in NR, timer handling, and support for SRB1/2 | Sony Europe B.V. |
| R2-2103715 | Non-SDT data transmission | CMCC |
| R2-2103796 | Subsequent small data transmission | InterDigital |
| R2-2103867 | Non-SDB handling during the SDT procedure | Apple |
| R2-2103868 | Control plane aspects on the SDT procedure | Apple |
| R2-2103904 | Control plane common aspects for SDT | Huawei, HiSilicon |
| R2-2103970 | CP and configuration aspects for small data | InterDigital |
| R2-2103971 | Report of [Post113-e][503][SDT] T319, cell reselection and re-establishment | InterDigital |
| R2-2103972 | [Draft] LS to SA WG3 on re-use of same NCC and I-RNTI value for RRC Resume procedure in different cells during small data transmission procedure. | InterDigital |
| R2-2103989 | Discussion on switching to non-SDT procedure | LG Electronics Inc. |
| R2-2103991 | Discussion on cell reselection during SDT | LG Electronics Inc. |
| R2-2104204 | Resuming non-SDT RBs and indication | LG Electronics Inc. |
| R2-2104221 | Discussion on the support of the RRC-less SDT | Xiaomi Communications, Intel Corporation, ASUSTeK, Fujitsu, MediaTek, Apple, Spreadtrum Communications |
| R2-2104222 | Technical details of the RRC-less SDT | Xiaomi Communications, ASUSTeK, Fujitsu, Spreadtrum Communications |
| R2-2104396 | LS to SA3 on Small data transmissions | InterDigital |
| R2-2104397 | LS to CT1 on Small data transmission | Intel |
| R2-2104399 | Summary of offline [AT113bis-e][504][SDT] LS to CT1 (Intel) | Intel Corporation |
| R2-2104401 | LS to SA3 on Small data transmissions | RAN2 |
| R2-2104644 | LS to CT1 on Small data transmission | RAN2 |
| 8.6.4 | Aspects specific to RACH based schemes | |
| R2-2102710 | Details of RACH bsaed Small Data Transmission | Samsung Electronics Co., Ltd |
| R2-2102752 | Discussion on RACH based SDT | OPPO |
| R2-2102757 | Supporting Small Data Transmission via RA Procedure | vivo |
| R2-2102847 | Fallback issue for 2-step RA based small data transmission | Sharp |
| R2-2103020 | Open issues for RACH based SDT | ZTE Corporation, Sanechips |
| R2-2103104 | Considerations on Procedures without Anchor Relocation | CATT |
| R2-2103105 | Analysis on Search Space of RA-SDT | CATT |
| R2-2103252 | Discussion on RACH-based SDT | Spreadtrum Communications |
| R2-2103264 | PDCCH monitoring in subsequent data transmission period | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103403 | Analysis on open issues of RA based SDT | Lenovo, Motorola Mobility |
| R2-2103433 | Discussion on RACH based NR small data transmission | Qualcomm Incorporated |
| R2-2103456 | Discussion on RO configuration between SDT and non-SDT | ASUSTeK |
| R2-2103519 | RACH based SDT | Ericsson |
| R2-2103529 | Details of context fetch and data forwarding | Nokia, Nokia Shanghai Bell |
| R2-2103580 | Discussion on context fetch and anchor relocation | Sony Europe B.V. |
| R2-2103716 | Anchor relocation and context fetch | CMCC |
| R2-2103869 | Subsequent data transmission for SDT | Apple |
| R2-2103903 | Small data transmission with RA-based schemes | Huawei, HiSilicon |
| 8.6.5 | Aspects specific to CG based schemes | |
| R2-2102711 | Details of Configured Grant based Small Data Transmission | Samsung Electronics Co., Ltd |
| R2-2102753 | Discussion on CG based SDT | OPPO |
| R2-2102758 | Supporting Small Data Transmission via CG configuration | vivo |
| R2-2102843 | On Configured Grant aspects for SDT | Intel Corporation |
| R2-2103021 | Open issues for CG based SDT | ZTE Corporation, Sanechips |
| R2-2103199 | PDCCH monitoring after TAT expiry | Fujitsu |
| R2-2103265 | CG-SDT based on beam operation | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103367 | Aspects specific to CG based SDT | Nokia, Nokia Shanghai Bell |
| R2-2103404 | Consideration on CG based small data transmission | Lenovo, Motorola Mobility |
| R2-2103434 | Discussion on CG based NR small data transmission | Qualcomm Incorporated |
| R2-2103457 | Beam selection for CG-SDT | ASUSTeK |
| R2-2103520 | Details of CG based SDT | Ericsson |
| R2-2103532 | Small data transmission with CG-based scheme | Huawei, HiSilicon |
| R2-2103533 | Report from [POST113-e][504][SDT] CG Open Issues | Huawei, HiSilicon |
| R2-2103581 | Details of CG-based scheme for SDT in NR | Sony Europe B.V. |
| R2-2103795 | CG-based SDT | InterDigital |
| R2-2104223 | Remaining issues of CG SDT | Xiaomi Communications |
| R2-2104241 | On CG Resource Configuration in Small Data enhancement | China Telecommunications |
| 8.7.1 | Organizational | |
| R2-2102890 | Work planning for R17 SL relay | OPPO, CMCC |
| R2-2104299 | Work planning for R17 SL relay | OPPO, CMCC |
| 8.7.2 | Relay discovery | |
| R2-2102687 | Discussion on relay discovery | Qualcomm Incorporated |
| R2-2102698 | Discovery for Sidelink U2N Relay | CATT |
| R2-2102806 | Discovery Procedure for sidelink relay | InterDigital |
| R2-2102978 | Discussion on Relay discovery in Sidelink Relay | ZTE Corporation, Sanechips |
| R2-2103000 | Left issues for SL discovery | Ericsson |
| R2-2103006 | Discussion on NR sidelink relay discovery | OPPO |
| R2-2103010 | NR Sidelink Relaying Discovery | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103071 | SL Relay Discovery Aspects | Intel Corporation |
| R2-2103085 | SL relay discovery message | Samsung |
| R2-2103205 | Discussion on sidelink relay discovery | SHARP Corporation |
| R2-2103227 | Discovery resources for sidelink relaying | Kyocera |
| R2-2103229 | Relay discovery considerations | Kyocera |
| R2-2103236 | Discussion on relay discovery | Spreadtrum Communications |
| R2-2103323 | Discussions on Relay discovery procedure | vivo |
| R2-2103389 | Relay Discovery in L2 and L3 U2N relay | Lenovo, Motorola Mobility |
| R2-2103424 | Sidelink Relay Discovery, Open Issues | Beijing Xiaomi Mobile Software |
| R2-2103493 | Support of discovery for sidelink relay | Huawei, HiSilicon |
| R2-2103498 | Restricted Sidelink Relay Discovery Within Sidelink Groupcast | Nokia Germany |
| R2-2103575 | On relay discovery | MediaTek Inc. |
| R2-2103856 | Evaluation of PC5 link quality based on relay discovery | Apple |
| R2-2103992 | Discovery message transmission | LG Electronics Inc. |
| R2-2104297 | Summary of 8.7.2 relay discovery | Huawei, HiSilicon |
| R2-2104413 | Summary of [609] | Ericsson |
| 8.7.3 | Relay re/selection | |
| R2-2102692 | Discussion on relay (re)selection | Qualcomm Incorporated |
| R2-2102699 | Sidelink Relay (Re)Selection | CATT |
| R2-2102807 | Relay selection and reselection | InterDigital |
| R2-2102960 | Further considerations on relay (re)selection | ETRI |
| R2-2102977 | Discussion on Relay selection in Sidelink Relay | ZTE Corporation, Sanechips |
| R2-2103001 | Aspects for SL relay selection and reselection | Ericsson |
| R2-2103007 | Discussion on NR sidelink relay (re-)selection | OPPO |
| R2-2103009 | NR Sidelink Relay (Re-)Selection | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103086 | SL relay selection and reselection triggering criteria | Samsung |
| R2-2103237 | Discussion on relay selection and reselection | Spreadtrum Communications |
| R2-2103311 | UE-to-Nwk Relay Discovery and (Re)selection for Path Switching in SL Relay | Nokia, Nokia Shanghai Bell |
| R2-2103324 | Discussions on Relay (re-)selection procedure | vivo |
| R2-2103390 | Relay (re)selection for L2 and L3 U2N case | Lenovo, Motorola Mobility |
| R2-2103422 | Sidelink Relay Reselection and Selection, proposal for outline procedure | Beijing Xiaomi Mobile Software |
| R2-2103423 | NR sidelink relay (re)selection | MediaTek Inc. |
| R2-2103584 | Relay (re)selection | Sony Europe B.V. |
| R2-2103667 | Discussion on relay selection and reselection | Nokia, Nokia Shanghai Bell |
| R2-2103717 | Consideration on Relay selection and reselection | CMCC |
| R2-2103739 | Discussion on SL Relay (re)selection | Intel Corporation |
| R2-2103884 | Discussion on sidelink relay (re)selection | Apple |
| R2-2103993 | Relay UE selection criterion using SL-unicast and discovery message | LG Electronics Inc. |
| R2-2103994 | Relay (re-)selection and path switching | LG Electronics Inc. |
| R2-2103995 | Discovery message contents and relay selection criteria | LG Electronics Inc. |
| R2-2104130 | Discussion on relay selection and reselection | Huawei, HiSilicon |
| R2-2104262 | Relay UE load as an additional AS criterion for relay (re-)selection | Philips International B.V. |
| R2-2104287 | Summary of Agenda Item 8.7.3 (relay selection/reselection) | Qualcomm Incorporated |
| R2-2104414 | Summary of [AT113bis-e][610][Relay] AS criteria for relay (re)selection (InterDigital) | InterDigital |
| R2-2104415 | Remaining proposals on relay (re)selection | Qualcomm Incorporated |
| R2-2104649 | LS on discovery and relay (re)selection | RAN2 |
| 8.7.4.1 | Control plane procedures | |
| R2-2102693 | RRC management procedures of L2 U2N relay | Qualcomm Incorporated |
| R2-2102695 | System information, paging delivery and UAC in L2 U2N relay | Qualcomm Incorporated |
| R2-2102700 | Control Plane Procedures of L2 Relay | CATT |
| R2-2102701 | Service Continuity for L2 U2N Relay | CATT |
| R2-2102747 | Discussion on Control Plane Aspects for L2 Relay | OPPO |
| R2-2102779 | Connection establishment for L2 UE-to-Network Relay | MediaTek Inc. |
| R2-2102780 | Further details on System Information Delivery | MediaTek Inc. |
| R2-2102809 | Connection Management for L2 UE to NW Relays | InterDigital |
| R2-2102810 | Control Plane Procedures for L2 UE to NW Relays | InterDigital |
| R2-2102891 | Left issues on RRC procedure for L2 U2N Relay | OPPO |
| R2-2102968 | Connection on L2 relay | Xiaomi communications |
| R2-2102969 | Discussion on resouce allocation for remote UE | Xiaomi communications |
| R2-2102974 | The connection management of SL relay | ZTE Corporation, Sanechips |
| R2-2102975 | Discussion on system information paging and access control | ZTE Corporation, Sanechips |
| R2-2103087 | Connection management in L2 U2N relay | Samsung |
| R2-2103088 | System information delivery via relay UE | Samsung |
| R2-2103203 | UE to Network Relay Connection Establishment | Futurewei |
| R2-2103231 | RRC state transitions in L2 relaying | Kyocera |
| R2-2103310 | Support of idle mode mobility for remote-UE in SL UE-to-Nwk relay | Nokia, Nokia Shanghai Bell |
| R2-2103325 | RRC Connection Management for L2 relay | vivo |
| R2-2103326 | Control Plane procedure for L2 SL Relay | vivo |
| R2-2103328 | Discussions on L2 and L3 relay co-existence | vivo |
| R2-2103458 | Discussion on RRC procedures for U2N Relay | ASUSTeK |
| R2-2103482 | SIB Handling in Sidelink UE-to-Nwk Relay | Nokia Germany |
| R2-2103662 | Discussion on control plane procedures for L2 sidelink relay | Ericsson |
| R2-2103663 | Discussion on service continuity for L2 sidelink relay | Ericsson |
| R2-2103718 | System information delivery for L2 U2N Relay | CMCC |
| R2-2103738 | Control plane procedures for L2 U2N relaying | Intel Corporation |
| R2-2103742 | Monitoring Paging by a U2N Relay | Lenovo, Motorola Mobility |
| R2-2103744 | SI acquisition, CN Registration and RNAU | Lenovo, Motorola Mobility |
| R2-2103857 | Discussion on QoS mechanism for Layer 2 UE-to-NW relay | Apple |
| R2-2103956 | Control plane multi-connectivity for NR Sidelink Relay UE | AT&T |
| R2-2103996 | L2 relay QoS handling procedure | LG Electronics Inc. |
| R2-2104126 | Service continuity of L2 U2N relay | Qualcomm communications-France |
| R2-2104131 | Discussion on the CP procedures for L2 Relay | Huawei, HiSilicon |
| R2-2104132 | Discussion on path switch for L2 UE to NW Relay | Huawei, HiSilicon |
| R2-2104245 | discussion on Paging and SI delivery for L2 U2N relay | ETRI |
| R2-2104405 | [AT113bis-e][603][Relay] Proposals from summary of agenda item 8.7.4.1 (ZTE) | ZTE |
| R2-2104503 | Summary document of AI 8.7.4.1 | ZTE |
| R2-2104654 | LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism | RAN2 |
| 8.7.4.2 | Protocol architecture | |
| R2-2102694 | Adaptation layer and E2E QoS handling of L2 U2N relay | Qualcomm Incorporated |
| R2-2102702 | Study on the Adaption Layer for L2 U2N Relay | CATT |
| R2-2102781 | Adaptation layer for PC5 at L2 UE-to-Network Relay | MediaTek Inc. |
| R2-2102808 | Discussion on L2 Relay Architecture and QoS | InterDigital |
| R2-2102892 | Left issues on adaptation layer for L2 U2N Relay | OPPO |
| R2-2102976 | Discussion on SL relay protocol architecture | ZTE Corporation, Sanechips |
| R2-2103002 | UP aspects for Layer 2 SL relay | Ericsson |
| R2-2103235 | Discussion on L2 Relay Architecture and QoS | Spreadtrum Communications |
| R2-2103327 | Adaptation Layer for L2 SL Relay | vivo |
| R2-2103459 | Discussion on presence of adaptation layer header for U2N Relay | ASUSTeK |
| R2-2103494 | Adaptation layer functionalities for L2 U2N relay | Huawei, HiSilicon |
| R2-2103514 | Adaptation layer and other protocol stack aspects for L2 relaying | Samsung Electronics GmbH |
| R2-2103719 | PC5 adaption layer for L2 U2N relay | CMCC |
| R2-2103720 | Consideration on Uu adaption layer | CMCC |
| R2-2103737 | Adaptation layer design for L2 U2N relaying | Intel Corporation |
| R2-2104406 | Report of [AT113bis-e][604][Relay] Proposals from summary of agenda item 8.7.4.2 | Futurewei |
| R2-2104505 | Summary document for AI 8.7.4.2 | Futurewei |
| 8.8.1 | Organizational | |
| R2-2103647 | SMBR enforcement in RAN | Ericsson |
| R2-2103694 | Work Plan for RAN Slicing WI | CMCC |
| 8.8.2 | Cell reselection | |
| R2-2102696 | Slice specific cell reselection | Qualcomm Incorporated |
| R2-2102762 | Considerations on slice based cell reselection | Beijing Xiaomi Software Tech |
| R2-2102773 | Considerations on contents of slice based reselection | KDDI Corporation |
| R2-2102831 | slice specific cell reselection | Intel Corporation |
| R2-2102988 | Considerations on slice-based cell reselection | Lenovo, Motorola Mobility |
| R2-2103159 | Discussion on slice based cell reselection | China Telecommunication |
| R2-2103213 | Consideration on slice-specific cell reselection | OPPO |
| R2-2103239 | Discussion on slice based cell reselection | Spreadtrum Communications |
| R2-2103269 | Cell (re)selection for RAN slicing | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103375 | Slice based cell reselection | vivo |
| R2-2103589 | Slice based Cell Reselection | Sony Europe B.V. |
| R2-2103621 | Discussion on slice based cell reselection | LG Electronics UK |
| R2-2103646 | On solution for RAN slicing enhancement | Ericsson |
| R2-2103668 | Slice-based cell reselection information | Nokia, Nokia Shanghai Bell |
| R2-2103695 | Discussion on slice based cell reselection | CMCC |
| R2-2103745 | Slice-specific system information for cell reselection | Google Inc. |
| R2-2103881 | Discussion on slice based cell reselection | Apple |
| R2-2103961 | System information contents for slice-aware cell reselection | Sharp |
| R2-2104004 | Discussion on slice based cell reselection under network control | Huawei, HiSilicon |
| R2-2104032 | Discussion on slice based Cell Reselection | CATT |
| R2-2104063 | Discussion on slice-aware cell reselection | ZTE corporation, Sanechips |
| R2-2104176 | Discussion on slice based cell reselection | Samsung Electronics Co., Ltd |
| R2-2104321 | Summary of [AT113bis-e][251][NR] Slice-specific cell reselection (Intel) | Intel |
| 8.8.3 | RACH | |
| R2-2102697 | Slice specific RACH | Qualcomm Incorporated |
| R2-2102761 | Considerations on slice based RACH configuration | Beijing Xiaomi Software Tech |
| R2-2102832 | Considerations of slice based RACH | Intel Corporation |
| R2-2102989 | Considerations on slice-based PRACH configuration | Lenovo, Motorola Mobility |
| R2-2103089 | Slice based RACH configuration | Samsung |
| R2-2103214 | Consideration on slice-specific RACH | OPPO |
| R2-2103240 | Consideration on slice based RACH configuration | Spreadtrum Communications |
| R2-2103376 | Slice based RACH configuration | vivo |
| R2-2103548 | RACH prioritisation for slices | Nokia, Nokia Shanghai Bell |
| R2-2103696 | Discussion on slice based RACH configuration | CMCC |
| R2-2103882 | Discussion on slice based RACH | Apple |
| R2-2104005 | Discussion on slice based RACH configuration | Huawei, HiSilicon |
| R2-2104019 | Analysis on slice based RACH configuration | CATT |
| R2-2104064 | Discussion on slice specific RACH resources and RACH prioritization | ZTE corporation, Sanechips |
| R2-2104099 | Slice-specific RA procedure | LG Electronics UK |
| R2-2104322 | Summary of [AT113bis-e][252][NR] Slice-specific RACH (CMCC) | CMCC |
| 8.9.1 | Organizational Scope and Requirements | |
| R2-2102621 | Reply LS on Paging Enhancement (R1-2102136; contact: MediaTek) | RAN1 |
| R2-2104356 | Reply LS on UE Sub-grouping for Paging Enhancement | RAN2 |
| 8.9.2 | Idle/inactive-mode UE power saving | |
| R2-2102680 | UE subgroup for paging reception | Qualcomm Incorporated |
| R2-2102704 | Paging Enhancements_UE Grouping | Samsung Electronics Co., Ltd |
| R2-2102705 | Paging Enhancements_DRX cycle for monitoring paging | Samsung Electronics Co., Ltd |
| R2-2102733 | Discussion on grouping-based paging | OPPO |
| R2-2102856 | Paging enhancement in idle inactive mode for power saving | vivo |
| R2-2102865 | Network assigned subgrouping | Intel Corporation |
| R2-2102871 | Procedure details for Network assigned subgrouping | Intel Corporation |
| R2-2102919 | UE sub-grouping mechanism with Paging Enhancement | CATT |
| R2-2103149 | Discussion on UE subgroup for paging | Xiaomi Communications |
| R2-2103258 | Paging Enhancement with UE Grouping | MediaTek Inc., CMCC |
| R2-2103259 | [Draft] Reply LS on UE Sub-grouping for Paging Enhancement | MediaTek Inc. |
| R2-2103266 | Discussion on indications for UE power saving | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103363 | UE subgrouping for paging enhancement | LG Electronics Inc. |
| R2-2103368 | Details on paging sub-grouping indication | Nokia, Nokia Shanghai Bell |
| R2-2103369 | Details on paging sub-grouping determination | Nokia, Nokia Shanghai Bell |
| R2-2103396 | Consideration on Idle/inactive-mode UE power saving | Lenovo, Motorola Mobility |
| R2-2103443 | Further discussion on UE grouping | ZTE Corporation, Sanechips |
| R2-2103585 | Discussion on the UE grouping mechanism | Huawei, HiSilicon |
| R2-2103587 | Discussion on other paging enhancements | Huawei, HiSilicon |
| R2-2103591 | Discussion on enhancements for idle/inactive-mode UE power saving | Sony Europe B.V. |
| R2-2103724 | Considerations on paging subgrouping | CMCC |
| R2-2103772 | Grouping methods for Paging | Ericsson |
| R2-2103773 | Group info signaled via Paging PDCCH | Ericsson |
| R2-2103833 | NR UE Power Save IDLE/INACTIVE Paging Grouping Schemes | Apple |
| R2-2103960 | Enhancement to paging reception with cross-slot scheduling | Qualcomm Incorporated |
| R2-2103975 | UE grouping paging enhancement | InterDigital |
| R2-2104163 | draft LS on Paging Enhancement for UE power saving | LG Electronics Inc. |
| R2-2104496 | Summary of Idle/Inactive-mode UE Power Saving (AI 8.9.2) | MediaTek Inc. |
| 8.9.3 | Other aspects RAN2 impacts | |
| R2-2102706 | TRS_CSIRS for RRC IDLE and RRC INACTIVE | Samsung Electronics Co., Ltd |
| R2-2102734 | Discussion on signaling aspects of TRS/CSI-RS occasion(s) for idle/inactive UEs | OPPO |
| R2-2102735 | power saving enhancement for connected mode UE | OPPO |
| R2-2102857 | Discussion on TRS CSI-RS in idle inactive mode | vivo |
| R2-2102858 | RAN2 impact on RLM/BFD relaxation for power saving | vivo |
| R2-2102863 | Discussion on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE | Xiaomi Communications |
| R2-2102864 | LS to RAN1 on TRS CSI-RS for RRC-IDLE and RRC-INACTIVE State UE | Xiaomi Communications |
| R2-2102867 | TRS/CSI-RS configuration for idle/inactive mode UE | Intel Corporation |
| R2-2103058 | TRS/CSI-RS configuration and enhancement to short message | Qualcomm Incorporated |
| R2-2103207 | TRS CSI-RS for idle and inactive mode UE | SHARP Corporation |
| R2-2103395 | TRS/CSI-RS configuration for Idle/inactive mode UE | Lenovo, Motorola Mobility |
| R2-2103442 | Futrther consideration on the CSI-RS/TRS for Idle/Inactive UE | ZTE Coporation, Sanechips |
| R2-2103496 | Potential TRS/CSI-RS occasion(s) | Nokia, Nokia Shanghai Bell |
| R2-2103586 | Discussion on potential TRS/CSI-RS | Huawei, HiSilicon |
| R2-2103596 | Discussion on TRS/CSI-RS configuration of idle/inactive-mode UEs | Sony Europe B.V. |
| R2-2103774 | TRS exposure to UEs in idle and inactive | Ericsson |
| R2-2103834 | NR UE Power Save TRS/CSI-RS Signaling for IDLE/INACTIVE UEs | Apple |
| R2-2104157 | Further Considerations on Configuration of TRS/CRI-RS | CATT |
| R2-2104277 | Considerations on TRS CSI-RS occasion(s) for idle inactive UE(s) | CMCC |
| R2-2104278 | Considerations on TRS CSI-RS occasion(s) for idle inactive UE(s) | CMCC |
| 8.10.1 | Organizational | |
| R2-2102602 | LS on extraterritorial use of MCC for satellite access (C1-210439; contact: Qualcomm) | CT1 |
| R2-2102617 | Reply LS on AN-PDB and PER targets for satellite access (R1-2102074; contact: Qualcomm) | RAN1 |
| R2-2102655 | Reply LS on timer for periodic network selection attempts in satellite access (S1-210357; contact: OPPO) | SA1 |
| R2-2102656 | Reply LS on extraterritorial use of MCC for satellite access (S1-210358; contact: Qualcomm) | SA1 |
| R2-2102679 | Reply LS on UE location aspects in NTN (S3i210282; contact: Tencastle) | SA3-LI |
| R2-2103469 | NR_NTN_solutions work plan | THALES |
| R2-2103698 | DRAFT LS to RAN1 about PCI issue in NTN | CMCC |
| R2-2103829 | Stage-3 running RRC CR for NTN Rel-17 | Ericsson |
| R2-2103969 | Stage 3 running CR 38.321 - RAN2#113bis-e | InterDigital |
| R2-2104289 | Stage-3 running 304 CR for NTN | ZTE Corporation, Sanechips |
| R2-2104622 | LS on PDB for new 5QI (S2-2103552; contact: Ericsson) | SA2 |
| 8.10.2 | User Plane | |
| R2-2103968 | MAC open issues - RAN2#113bis-e | InterDigital |
| 8.10.2.1 | RACH aspects | |
| R2-2102738 | Discussion on the left RACH issues in NTN | OPPO |
| R2-2102932 | Considerations on RACH procedure enhancements in NTN | CAICT |
| R2-2103053 | Start offset for RAR window and contention resolution timer | Qualcomm Incorporated |
| R2-2103074 | Timing Compensation, 4-Step RA Enhancements, and RA Resource Selection for an NTN | Samsung Research America |
| R2-2103261 | Triggering of UE-specific TA report | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103263 | BSR over 2-step RACH | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103406 | Considerations on TA pre-compensation capability for RACH in NTN | Lenovo, Motorola Mobility |
| R2-2103407 | Further clarification and consideration for RA type selection | Lenovo, Motorola Mobility |
| R2-2103460 | BSR over 2-step RA | ASUSTeK |
| R2-2103630 | Report of [POST113-e][106][NTN] MAC aspects (Huawei) | Huawei, HiSilicon |
| R2-2103839 | Considerations for RA Type and TA Timer MAC Enhancements in Non Terrestrial Networks | Apple |
| R2-2103951 | On Random Access in NTNs | Ericsson |
| R2-2104141 | Discussion on RA type selection and TA report | LG Electronics Inc. |
| R2-2104146 | NTN 2-step RACH selection enhancements | Convida Wireless |
| R2-2104190 | Consideration on Random Access and TA | ZTE Corporation, Sanechips |
| R2-2104362 | Summary of offline 103 - [NTN] RACH aspects - first round | Oppo |
| R2-2104370 | Summary of offline 103 - [NTN] RACH aspects - second round | OPPO |
| R2-2104376 | LS on TA pre-compensation | RAN2 |
| 8.10.2.2 | Other MAC aspects | |
| R2-2102739 | Discussion on HARQ impact in NTN | OPPO |
| R2-2102823 | Round trip delay offset for configured grant timers | MediaTek Inc. |
| R2-2102824 | On disabling uplink HARQ retransmission and associated LCP impacts | MediaTek Inc. |
| R2-2102951 | Discussion on UL Scheduling Enhancements in NR NTN | CATT |
| R2-2102952 | Discussion on HARQ Aspects in NTN | CATT |
| R2-2103054 | Support of dynamic disabling of UL HARQ retransmission | Qualcomm Incorporated |
| R2-2103075 | HARQ Stalling, RNTI Enhancements, Enhanced UL Scheduling, and Logical Channel Prioritization for an NTN | Samsung Research America |
| R2-2103175 | HARQ related issues | Beijing Xiaomi Mobile Software |
| R2-2103230 | On DRX and LCP impact for NTN | Nokia, Nokia Shanghai Bell |
| R2-2103232 | Discussion on UL scheduling enhancements for NTN | Nokia, Nokia Shanghai Bell |
| R2-2103262 | HARQ retransmission schemes in NTN | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103445 | Co-existence issue of BSR over CG and BSR over 2-step RACH | PANASONIC R&D Center Germany |
| R2-2103446 | DRX impact of disabling HARQ feedback and uplink retransmission | PANASONIC R&D Center Germany |
| R2-2103599 | Other MAC enhancements in NTN | Sony Europe B.V. |
| R2-2103629 | Further consideration on HARQ and LCP in NTN | Huawei, HiSilicon |
| R2-2103725 | Left Issues for HARQ operation in NTN | CMCC |
| R2-2103826 | TA Adjustment in RRC_CONNECTED state | NEC Telecom MODUS Ltd. |
| R2-2103950 | On scheduling, HARQ, and DRX for NTNs | Ericsson |
| R2-2103967 | UL HARQ RTT timer in NTN | InterDigital |
| R2-2104038 | Discussion on MAC timers about UL scheduling in NTN | CAICT |
| R2-2104144 | Discussion on UL scheulding and UL retranmission | LG Electronics Inc. |
| R2-2104191 | Consideration on HARQ aspects | ZTE Corporation, Sanechips |
| R2-2104363 | Summary of offline 104 - [NTN] Other MAC aspects - first round | Ericsson |
| R2-2104369 | Summary of [AT113bis-e][104][NTN] Other MAC aspects - second round | Ericsson (rapporteur) |
| 8.10.2.3 | RLC and PDCP aspects | |
| R2-2103827 | RLC t-Reassembly timer configuration | NEC Telecom MODUS Ltd. |
| R2-2103964 | On RLC t-Reassembly for NTN | Sequans Communications |
| R2-2104286 | Report of [POST113-e][107][NTN] RLC and PDCP Aspects (Samsung) | Samsung |
| R2-2104499 | Report of [POST113-e][107][NTN] RLC and PDCP Aspects (Samsung) | Samsung |
| 8.10.3.1 | Earth fixed/moving beams related issues | |
| R2-2102740 | Discussion on TAC update | OPPO |
| R2-2102990 | Issues on the TAC update due to satellite movement | PANASONIC R&D Center Germany |
| R2-2103008 | Signalling Solution for Feeder Link Switching of NTN | VODAFONE Group Plc |
| R2-2103055 | TAC update procedure | Qualcomm Incorporated |
| R2-2103076 | TAC Management and Neighbor Search in an NTN | Samsung Research America |
| R2-2103134 | Discussion on TAC aspects for NTN | Xiaomi |
| R2-2103244 | Discussion on TAC updating in NTN | Spreadtrum Communications |
| R2-2103307 | Contents of ephemeris including beam type information | LG Electronics Inc. |
| R2-2103334 | On Feeder Link Mobility in Transparent Satellite Payload Scenarios | Nokia, Nokia Shanghai Bell |
| R2-2103627 | Discussion on decoupled cell ID | Huawei, HiSilicon |
| R2-2103628 | Discussion on remaining issues on soft TAU | Huawei, HiSilicon |
| R2-2103699 | Discussion on SI modification for TAC Update | CMCC |
| R2-2103747 | Aspects for Earth fixed and Earth moving beams for NTN | Ericsson |
| R2-2103749 | Aspects concerning soft TAC switch | Ericsson |
| R2-2103836 | Analysis of Mobility Management with Earth Fixed and Earth Moving Beams/Cells in NTN Networks | Apple |
| R2-2103912 | NR-NTN: Multi-TAI Broadcast | Fraunhofer IIS, Fraunhofer HHI |
| R2-2104364 | Summary of offline 105 - [NTN] TAC update - first round | Huawei |
| R2-2104371 | Summary of offline 105 - [NTN] TAC update - second round | Huawei |
| R2-2104377 | LS on multiple TACs per PLMN | RAN2 |
| 8.10.3.2 | Idle/Inactive mode | |
| R2-2102741 | Discussion on idle/inactive mode procedures in NTN | OPPO |
| R2-2102825 | On Cell-Reselection in NR-NTN | MediaTek Inc. |
| R2-2102826 | On Soft-switch based Tracking Area Updates in NR-NTN | MediaTek Inc. |
| R2-2102953 | Leftover issues on IDLE and inactive mode | CATT |
| R2-2103077 | Cell Reselection, System Information, and Paging Enhancements for an NTN | Samsung Research America |
| R2-2103135 | Cell selection and reselection enhancements for NTN | Xiaomi |
| R2-2103245 | Issues on cell selection and reselection in NTN | Spreadtrum Communications |
| R2-2103408 | Ephemeris provision and network type indication for NTN | Lenovo, Motorola Mobility |
| R2-2103461 | PLMN separation for NTN & TN | ASUSTeK |
| R2-2103597 | Idle mode enhancement in NTN | Sony Europe B.V. |
| R2-2103631 | WF for cell reselection in NTN | Huawei, HiSilicon, BT Plc, CAICT, China Telecom |
| R2-2103837 | Cell Selection And Cell Reselection Solutions for Non Terrestrial Networks | Apple, British Telecom |
| R2-2103838 | Considerations on ephemeris database and parameter distribution to UEs in Non Terrestrial Networks | Apple |
| R2-2103965 | Cell reselection in NTN | InterDigital |
| R2-2103966 | Ephemeris in NTN | InterDigital |
| R2-2104066 | Further consideration on cell selection and reselection in NTN | ZTE corporation, Sanechips |
| R2-2104147 | NTN indication and idle mode enhancements | Convida Wireless |
| R2-2104148 | NTN Cell Selection and Idle Mode Enhancements | Convida Wireless |
| R2-2104149 | NTN Cell (re)selection and idle mode enhancements | Convida Wireless |
| R2-2104210 | Understanding on the newly introduced Access Technology identifier for NTN | ZTE corporation, Sanechips |
| 8.10.3.3 | Connected mode | |
| R2-2102742 | Discussion on mobility management for connected mode UE in NTN | OPPO |
| R2-2102827 | Mobility for NTN-TN scenarios | MediaTek Inc. |
| R2-2102866 | Report of [post113-e][108][NTN] SMTC and measurement gap | Intel Corporation |
| R2-2102954 | Further discuss CHO solutions for NR NTN | CATT |
| R2-2103056 | Configuration and execution of CHO | Qualcomm Incorporated |
| R2-2103057 | Multiple SMTC configurations | Qualcomm Incorporated |
| R2-2103078 | Handover Enhancements for an NTN | Samsung Research America |
| R2-2103181 | Discussion on conditional handover in NTN | Xiaomi Communications |
| R2-2103182 | Discussion on measurement in NTN | Xiaomi Communications |
| R2-2103308 | Connected mode enhancements in NTN | LG Electronics Inc. |
| R2-2103335 | On Connected mode mobility for NTN | Nokia, Nokia Shanghai Bell |
| R2-2103336 | Post-[108][NTN] views on SMTC and measurement gaps | Nokia, Nokia Shanghai Bell |
| R2-2103356 | Discussion on updating the timing for SMTC and measurement gap configuration | ITRI |
| R2-2103362 | Measurement window enhancements for NTN cell | LG Electronics Inc. |
| R2-2103409 | Enhancement to measurement reporting in NTN | Lenovo, Motorola Mobility |
| R2-2103410 | CHO in NTN system | Lenovo, Motorola Mobility |
| R2-2103465 | Configuration of CHO in NTN | China Telecom, Huawei, HiSilicon |
| R2-2103600 | Mobility management in NTN | Sony Europe B.V. |
| R2-2103602 | Cell coverage spillage over multiple countries issue in NTN | Sony Europe B.V. |
| R2-2103620 | Service continuity between NTN and TN | Hughes/EchoStar |
| R2-2103632 | WF for CHO in NTN | Huawei, HiSilicon, BT Plc, CAICT, CMCC |
| R2-2103700 | Discussion on SMTC/Gap enhancements for NTN | CMCC |
| R2-2103701 | Consideration on signaling issues for mobility enhancements | CMCC |
| R2-2103702 | Discussion on service continuity between NTN and TN | CMCC |
| R2-2103751 | Connected mode aspects for NTN | Ericsson |
| R2-2103825 | Discussion on CHO for NTN | NEC Telecom MODUS Ltd. |
| R2-2103976 | Service continuity between NTN and TN | Hughes/EchoStar, Thales, BT Plc, Turkcell, Vodafone, ESA, Inmarsat |
| R2-2104065 | Further consideration on CHO in NTN | ZTE corporation, Sanechips |
| R2-2104145 | SMTC and MG configuration for NTN | Convida Wireless |
| R2-2104153 | NTN ANR enhancements | Convida Wireless |
| R2-2104200 | Measurement enhancement for NTN | ETRI |
| R2-2104365 | Summary of offline 106 - [NTN] SMTC and gaps - first round | Intel |
| R2-2104366 | Summary of offline 107 - [NTN] CHO aspects - first round | Nokia |
| R2-2104372 | Summary of offline 106 - [NTN] SMTC and gaps - second round | Intel Corporation |
| R2-2104373 | Report from [113bis-e][107][NTN] CHO aspects (Nokia) – Phase 2 | Nokia, Nokia Shanghai Bell |
| 8.10.3.4 | LCS aspects | |
| R2-2102955 | Discussion on network selection impact on LCS | CATT |
| 8.11.1 | Organizational | |
| R2-2102665 | LS on Scheduling Location in Advance to reduce Latency (S2-2102048; contact: Qualcomm) | SA2 |
| R2-2102959 | Work plan on Rel-17 positioning Work item | Intel Corporation, CATT, Ericsson |
| 8.11.2 | Latency | |
| R2-2102789 | Discussion on latency enhancement for R17 positioning | vivo |
| R2-2102849 | Consideration on latency reduction solutions | Intel Corporation |
| R2-2102925 | Consideration on Latency Optimization of Assistance Data | CATT |
| R2-2103131 | Positioning enhancements on latency reduction | Xiaomi |
| R2-2103144 | Consideration of the latency reduction regarding the scheduling the localization in advance | OPPO |
| R2-2103382 | Positioning Latency Reduction Enhancements | Lenovo, Motorola Mobility |
| R2-2103541 | Discussion on positioning latency | Huawei, HiSilicon |
| R2-2103614 | Considerations on positioning latency | Sony Europe B.V. |
| R2-2103785 | Enhancements for Latency Reduction | InterDigital, Inc. |
| R2-2103898 | Scheduling Location in Advance to reduce Latency | Qualcomm Incorporated |
| R2-2103899 | [draft] Response LS on Scheduling Location in Advance to reduce Latency | Qualcomm Incorporated |
| R2-2103914 | Reducing Latency for Positioning procedures | Ericsson |
| R2-2104179 | Latency reduction via configured grant for positioning | Samsung R&D Institute UK |
| R2-2104181 | Latency reduction via measurement gap signalling optimization | Samsung R&D Institute UK |
| R2-2104274 | Disucssion on latency reduction | ZTE Corporation, Sanechips |
| R2-2104275 | Discussion on preiodic PRS measurement | ZTE Corporation, Sanechips |
| R2-2104420 | Response LS on Scheduling Location in Advance to reduce Latency | RAN2 |
| R2-2104498 | Summary of Agenda Item 8.11.2: Positioning Latency Enhancements | Qualcomm Incorporated |
| R2-2104586 | Summary of [AT113bis-e][612][POS] LS to SA2 on scheduled location time | Qualcomm Incorporated |
| R2-2104587 | [draft] Response LS on Scheduling Location in Advance to reduce Latency | Qualcomm Incorporated |
| 8.11.3 | RRC Inactive | |
| R2-2102788 | Discussion DL positioning support in RRC_INACTIVE states | vivo |
| R2-2102798 | Discussion on DL Positioning methods in RRC_INACTIVE state | OPPO |
| R2-2102799 | Discussion on UL Positioning methods in RRC_INACTIVE state | OPPO |
| R2-2102850 | Support of Positioning in RRC_INACTIVE | Intel Corporation |
| R2-2102926 | Considerations on Positioning for UEs in RRC_INACTIVE state | CATT |
| R2-2103130 | Positioning enhancements on RRC Inactive UE | Xiaomi |
| R2-2103383 | On Positioning in RRC_INACTIVE state | Lenovo, Motorola Mobility |
| R2-2103537 | Discussion on positioning in RRC INACTIVE state | Huawei, HiSilicon |
| R2-2103611 | Considerations on positioning RRC Inactive | Sony Europe B.V. |
| R2-2103612 | Considerations on positioning RRC Inactive | Sony Europe B.V. |
| R2-2103786 | Positioning in RRC INACTIVE state | InterDigital, Inc. |
| R2-2103900 | Positioning of UEs in RRC Inactive State | Qualcomm Incorporated |
| R2-2103915 | On Usage of SDT for Positioning | Ericsson |
| R2-2103997 | Considerations on positioning in RRC_INACTIVE | Nokia, Nokia Shanghai Bell |
| R2-2104129 | UL and DL+UL NR positioning methods | vivo Mobile Communication Co., |
| R2-2104183 | Support of positioning result reporting in Inactive state | Samsung R&D Institute UK |
| R2-2104272 | Discussion on DL INACTIVE positioning | ZTE Corporation, Sanechips |
| R2-2104280 | Discussion DL positioning support in RRC_INACTIVE states | vivo Mobile Communication Co., |
| R2-2104282 | Discussion DL positioning support in RRC_INACTIVE states | vivo Mobile Communication Co., |
| R2-2104495 | Summary for AI 8.11.3 RRC INACTIVE | vivo |
| 8.11.4 | On-demand PRS | |
| R2-2102790 | discuss on-demand PRS | vivo |
| R2-2102797 | Discussion on on-demand DL-PRS | OPPO |
| R2-2102851 | On-Demand PRS transmission | Intel Corporation |
| R2-2102927 | Discussion on on-demand PRS | CATT |
| R2-2103132 | Discussion on on-demand DL PRS procedure | Xiaomi |
| R2-2103250 | Discussion on the enhancements of on-demand PRS | Spreadtrum Communications |
| R2-2103384 | On-Demand DL-PRS Support | Lenovo, Motorola Mobility |
| R2-2103538 | Discussion on on-demand PRS | Huawei, HiSilicon |
| R2-2103542 | Summary of AI 8.11.4 for on-demand PRS | Huawei, HiSilicon |
| R2-2103564 | On-demand PRS | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103613 | Considerations on positioning PRS On-demand | Sony Europe B.V. |
| R2-2103787 | Procedures for On-demand PRS | InterDigital, Inc. |
| R2-2103858 | Discussion on the signaling support for on-demand PRS | Apple |
| R2-2103901 | On-demand PRS | Qualcomm Incorporated |
| R2-2103916 | On demand PRS for energy savings | Ericsson |
| R2-2103998 | On-demand PRS transmission considerations | Nokia, Nokia Shanghai Bell |
| R2-2103999 | Latency enhancement to on-demand PRS functionality | Nokia, Nokia Shanghai Bell |
| R2-2104142 | UE-initiated requests for on-demand PRS | Convida Wireless |
| R2-2104184 | Support of on-demand DL PRS for positioning efficiency | Samsung R&D Institute UK |
| R2-2104276 | Discussion on on demand PRS | ZTE Corporation, Sanechips |
| R2-2104500 | On demand PRS for energy savings | Ericsson |
| R2-2104507 | Summary of AI 8.11.4 for on-demand PRS | Huawei, HiSilicon |
| R2-2104508 | On demand PRS for energy savings | Ericsson |
| 8.11.5 | GNSS positioning integrity | |
| R2-2102787 | Discussion on methodologies for network-assisted and UE-assisted integrity | vivo |
| R2-2102928 | Discussion on signalling and procedures to support GNSS positioning integrity | CATT |
| R2-2102994 | Signalling and Procedures for Positioning Integrity Support | Nokia, Nokia Shanghai Bell |
| R2-2103133 | Discussion on signalling and procedures for GNSS positioning integrity | Xiaomi |
| R2-2103145 | Introduction of positioning integrity related timer | OPPO |
| R2-2103539 | Discussion on network-assisted and UE-assisted integrity | Huawei, HiSilicon |
| R2-2103567 | UE-aided detection of threat to GNSS systems and assistance data signalling | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103750 | Guiding framework on integrity concepts for A-GNSS positioning | ESA |
| R2-2103788 | Procedures for GNSS positioning integrity | InterDigital, Inc. |
| R2-2103917 | GNSS Integrity aspects of GNSS local environment and UE feared events | Ericsson |
| R2-2103954 | Considerations on Positioning Integrity Determination | Swift Navigation, Intel Corporation, Ericsson |
| R2-2104189 | Consideration on the signalling design for Positioning Integrity | Samsung R&D Institute UK |
| R2-2104273 | Discussion on positioning integrity | ZTE Corporation, Sanechips |
| R2-2104291 | Summary of 8.11.5 GNSS positioning integrity | InterDigital, Inc. |
| R2-2104497 | Summary of 8.11.5 GNSS positioning integrity | InterDigital, Inc. |
| 8.11.6 | Other | |
| R2-2102929 | Discussion on Measurement Time Windows for accuracy improvement | CATT |
| R2-2103540 | Discussion on R17 positioning enhancement | Huawei, HiSilicon |
| R2-2103789 | Positioning during mobility and in RRC INACTIVE | InterDigital, Inc. |
| R2-2103902 | Signalling and Procedures for supporting Reference Location Devices | Qualcomm Incorporated |
| R2-2103918 | On High Accuracy Aspects | Ericsson |
| 8.12.1 | Organizational | |
| R2-2102678 | LS on Unified Access Control (UAC) for RedCap (RP-210919; contact: Nokia) | RAN |
| R2-2102964 | RAN2 work plan for RedCap WI | Ericsson |
| 8.12.2.1 | Definition of RedCap UE type and reduced capabilities | |
| R2-2103249 | Discussion on L2 buffer size reduction for Redcap UE | Spreadtrum Communications |
| 8.12.2.2 | Identification, access and camping restrictions | |
| R2-2102859 | Identification and access restrictions for RedCap UEs | vivo, Guangdong Genius |
| R2-2102947 | Camping restriction and cell selection criterion | DENSO CORPORATION |
| R2-2103062 | Methods for barring and for capability reporting | Sierra Wireless, S.A. |
| R2-2103279 | Access control for RedCap UEs | Samsung |
| R2-2103506 | Early identification and SI indication | NEC |
| R2-2103973 | Identification and restriction of RedCap UE | InterDigital |
| 8.12.3.1 | eDRX cycles | |
| R2-2102681 | Discussions on eDRX configuration | Qualcomm Incorporated |
| R2-2102736 | Discussion on eDRX for RedCap UEs | OPPO |
| R2-2102852 | Extend paging DRX for RedCap devices | Intel Corporation |
| R2-2102862 | Discussion on e-DRX for Redcap Devices | Xiaomi Communications |
| R2-2102962 | Work on eDRX for RedCap UEs | DENSO CORPORATION |
| R2-2102965 | Discussion of eDRX for RedCap | Ericsson |
| R2-2103039 | Discussion on eDRX for RedCap UE | ZTE Corporation, Sanechips |
| R2-2103112 | Discussion On eDRX for NR RRC Inactive and Idle | CATT |
| R2-2103530 | eDRX for REDCAP | Nokia, Nokia Shanghai Bell |
| R2-2103622 | eDRX for RedCap UEs in RRC_IDLE/RRC_INACTIVE | LG Electronics UK |
| R2-2103707 | Discussion on eDRX for RedCap | CMCC |
| R2-2103783 | Further considerations for eDRX | MediaTek Inc. |
| R2-2103887 | RedCap UE power-saving with 2.56 DRX cycle | Apple |
| R2-2104059 | eDRX for RedCap UE | Huawei, HiSilicon |
| R2-2104360 | Summary of offline 101 - [REDCAP] eDRX cycles - first round | Intel |
| R2-2104367 | Summary of offline 101 - [REDCAP] eDRX cycles - second round | Intel Corporation |
| R2-2104374 | LS on introducing extended DRX for RedCap UEs | RAN2 |
| 8.12.3.2 | RRM relaxations | |
| R2-2102682 | RRM relaxation enhancements for stationary UEs | Qualcomm Incorporated |
| R2-2102737 | Discussion on RRM relax for RedCap UEs | OPPO |
| R2-2102853 | RRM measurement relaxation criteria for RedCap devices | Intel Corporation |
| R2-2102860 | Discussion on RRM relaxation criteria for neighboring cells | vivo, Guangdong Genius |
| R2-2102966 | Mechanisms for RRM relaxation for RedCap | Ericsson |
| R2-2103038 | RRM relaxation for RedCap UE | ZTE Corporation, Sanechips |
| R2-2103113 | Discussion On RRM Relaxations | CATT |
| R2-2103150 | Discussion on RRM relaxation for RedCap UE | Xiaomi Communications |
| R2-2103206 | RRM relaxation in RRC_CONNECTED for RedCap UEs | SHARP Corporation |
| R2-2103309 | RRM relaxation for RedCap devices | LG Electronics Inc. |
| R2-2103402 | RRM relaxation for stationary UE with reduced capability | Lenovo, Motorola Mobility |
| R2-2103495 | On RRM relaxations for REDCAP | Nokia, Nokia Shanghai Bell |
| R2-2103691 | Discussion on the RRM relaxation for RedCap Ues | CMCC |
| R2-2103781 | Discussion on RRM Relaxation of REDCAP UE | China Telecommunications |
| R2-2103784 | On RRM relaxation for RedCap devices | MediaTek Inc. |
| R2-2103888 | RRM relaxation down selection of options for RedCap | Apple |
| R2-2103974 | RRM relaxation for RedCap UE | InterDigital |
| R2-2104060 | RRM measurement relaxation for RedCap UE | Huawei, HiSilicon |
| R2-2104081 | RRM relaxation criteria for RedCap devices | Samsung |
| R2-2104361 | Summary of offline 102 - [REDCAP] RRM relaxations - first round | Qualcomm |
| R2-2104368 | Summary of offline 102 - [REDCAP] RRM relaxations - second round | Qualcomm |
| R2-2104375 | Summary of offline 102 - [REDCAP] RRM relaxations - third round | Qualcomm |
| 8.13.1 | Organizational | |
| R2-2102629 | Reply LS on on energy efficiency (R3-207014; contact: Ericsson) | RAN3 |
| R2-2102639 | LS on information needed for MRO in SCG Failure Report (R3-211332; contact: Samsung) | RAN3 |
| R2-2102640 | LS on the details of logging forms reported by the gNB-CU-CP, gNB-CU-UP and gNB-DU under measurement pollution conditions (R3-211334; contact: Ericsson) | RAN3 |
| 8.13.2.1 | Handover related SON aspects | |
| R2-2103065 | HO related SON changes | QUALCOMM Incorportated |
| R2-2103098 | Discussion on CHO and DAPS Aspect | CATT |
| R2-2103142 | Further consideration on handover related SON | OPPO |
| R2-2103157 | Discussion on CHO configuration optimization aspects | China Telecommunication |
| R2-2103164 | Discussion on signalling and content of DAPS HO report | vivo |
| R2-2103385 | SON Enhancements for CHO | Lenovo, Motorola Mobility |
| R2-2103386 | SON Enhancement for DAPS Handover | Lenovo, Motorola Mobility |
| R2-2103550 | Further clarifications on MRO | Nokia, Nokia Shanghai Bell |
| R2-2103709 | Further consideration on SON Enhancement for CHO | CMCC |
| R2-2103710 | SON Enhancement for DAPS | CMCC |
| R2-2103731 | Discussion on handover related SON aspects | Huawei, HiSilicon |
| R2-2103933 | Introducing additional CHO related failure/ success info, including multiple event | Samsung Telecommunications |
| R2-2103944 | Handover-related SON aspects | Ericsson |
| R2-2103945 | [Post113-e][851][NR17 SON/MDT] HO related SON changes (Ericsson) | Ericsson |
| R2-2104045 | SON Enhancements for DAPS HO | Samsung |
| R2-2104070 | Discussion on RLF report for DAPS | SHARP Corporation |
| R2-2104192 | Remaining issues on RLF report enhancements | ZTE Corporation, Sanechips |
| R2-2104438 | [AT113bis-e][801][NR/R17 SON/MDT] Successful HO Report (Ericsson) | Ericsson |
| R2-2104502 | Summary of AI 8.13.2.1 Handover related SON aspects | Ericsson |
| R2-2104572 | [AT113bis-e][801][NR/R17 SON/MDT] Successful HO Report (Ericsson) | Ericsson |
| 8.13.2.2 | 2-step RA related SON aspects | |
| R2-2103093 | Report of [Post113-e][852][NR17 SON/MDT] 2 step RA and other SON changes (CATT) | CATT |
| R2-2103094 | [Draft] Reply LS on RACH report for 2-step RACH | CATT |
| R2-2103165 | Discussion on signalling model of 2-step RACH report | vivo |
| R2-2103421 | Discussion on 2-step RACH reporting in SON | OPPO |
| R2-2103551 | Remaining Issues and New Aspects in 2-step NR UE Report | Nokia, Nokia Shanghai Bell |
| R2-2103711 | SON Enhancement for 2-step RA | CMCC |
| R2-2103732 | Discussion on 2 step RA related SON aspects | Huawei, HiSilicon |
| R2-2103942 | 2-Step RA information for SON purposes | Ericsson |
| R2-2104055 | SON Enhancements for 2SRA | Samsung |
| R2-2104057 | Discussion on RA information for 2-step RA | SHARP Corporation |
| R2-2104193 | Remaining issues on RA related enhancements | ZTE Corporation, Sanechips |
| R2-2104292 | Summary of AI 8.13.2.2 | CATT |
| R2-2104439 | Report of [AT113b-e][802][NR/R17 SON/MDT] 2 step RA and other SON enhancements (CATT) | CATT |
| R2-2104536 | Report of [AT113b-e][802][NR/R17 SON/MDT] 2 step RA and other ?SON enhancements (CATT)? | CATT |
| R2-2104625 | Reply LS on RACH report for 2-step RACH | RAN2 |
| 8.13.2.3 | Other WID related SON features | |
| R2-2103066 | NR-U Related Enhancements | QUALCOMM Incorporated |
| R2-2103095 | Solution for the UE RACH Report for SN | CATT |
| R2-2103096 | Further Consideration on PSCell MHI | CATT |
| R2-2103099 | On Successful HO Report | CATT |
| R2-2103148 | Consideration on successful handover report and UE history information in EN-DC | OPPO |
| R2-2103298 | Discussion on signalling aspects of successful handover report | NEC |
| R2-2103387 | MRO for Inter-RAT handover | Lenovo, Motorola Mobility |
| R2-2103388 | MRO for fast MCG link recovery | Lenovo, Motorola Mobility |
| R2-2103552 | Discussion on other SON aspects | Nokia, Nokia Shanghai Bell |
| R2-2103553 | MPE impact on MRO | Nokia, Nokia Shanghai Bell |
| R2-2103712 | Discussion on Successful Handover Report | CMCC |
| R2-2103713 | Further consideration on UL-DL coverage mismatch | CMCC |
| R2-2103733 | Discussion on other SON aspects | Huawei, HiSilicon |
| R2-2103755 | Discussion on enhancement of RLF report | NTT DOCOMO, INC. |
| R2-2103943 | Other WID related SON features | Ericsson |
| R2-2104056 | SON Enhancements for Successful HO Report | Samsung |
| R2-2104058 | Other SON Enhancements | Samsung |
| R2-2104071 | Successful HO report in DAPS | SHARP Corporation |
| R2-2104194 | Further considerations on successful HO report | ZTE Corporation, Sanechips |
| R2-2104195 | Consideration on RAN3 concerned issues | ZTE Corporation, Sanechips |
| R2-2104296 | Summary of AI 8.13.2.3 Other WID related SON features | vivo |
| 8.13.3.1 | Immediate MDT enhancements | |
| R2-2103064 | On the accuracy of M5 and M7 measurements in split-bearer | QUALCOMM Incorporated |
| R2-2103100 | Further Consideration on Immediate MDT Enhancements | CATT |
| R2-2103166 | Support of immediate MDT in MR-DC | vivo |
| R2-2103810 | On Immediate MDT Enhancements | Ericsson |
| R2-2103985 | D1 in Immediate MDT | Nokia, Nokia Shanghai Bell |
| R2-2104006 | Report of [Post113-e][853][NR17 SON/MDT] IMM MDT | Huawei |
| R2-2104007 | Discussion on immediate MDT enhancements | Huawei, HiSilicon |
| R2-2104180 | Discussion on immediate MDT | OPPO |
| R2-2104295 | Summary of 8.13.3.1 Rel-17 Imm MDT | Huawei |
| R2-2104441 | Report of [AT113b-e][803][NR/R17 SON/MDT] IMM MDT | Huawei (Email rapporteur) |
| R2-2104442 | [Draft] LS on Rel-17 immediate MDT | Huawei |
| 8.13.3.2 | Logged MDT enhancements | |
| R2-2103063 | Logged Measurement Enhancements | QUALCOMM Incorporated |
| R2-2103097 | MDT enhancements for On-demand SI | CATT |
| R2-2103143 | Enhancements for logged MDT | OPPO |
| R2-2103501 | Discussion on recording SI related information | OPPO |
| R2-2103554 | Logged MDT in EN-DC and other enhancements | Nokia, Nokia Shanghai Bell |
| R2-2103697 | MDT for slice unavailability | CMCC |
| R2-2103708 | Report of [Post113-e][854][NR17 SON MDT] Logged MDT | CMCC |
| R2-2103811 | On logged MDT related enhancements | Ericsson |
| R2-2103930 | R17 Logged MDT issues (overwrite, IRAT/ MR-DC, logging non camping freqs, IDC and OSI) | Samsung Telecommunications |
| R2-2104008 | Discussion on logged MDT enhancements | Huawei, HiSilicon |
| R2-2104196 | Remaining issues on logging of on-demand SI request information | ZTE Corporation, Sanechips |
| R2-2104197 | On support MDT in NPN | ZTE Corporation, Sanechips |
| R2-2104431 | Summary for 8.13.3.2 Logged MDT enhancements | CMCC |
| R2-2104434 | Report of [AT113b-e][804][NR/R17 SON/MDT] Logged MDT (CMCC) | CMCC |
| 8.13.4 | L2 Measurements | |
| R2-2103156 | Discussion on introduction of the UE DL PDCP packet average delay measurement | China Telecommunication |
| R2-2103824 | On layer-2 measurements | Ericsson |
| R2-2104009 | Discussion on L2M | Huawei, HiSilicon |
| 8.14.1 | Organizational | |
| R2-2102633 | Conclusion of NR QoE Management and Optimizations for Diverse Services SI in RAN3 (R3-211234; contact: China Unicom) | RAN3 |
| R2-2102643 | Reply LS on QoE Measurement Collection for LTE (RP-210922; contact: Ericsson) | RAN |
| R2-2102760 | Workplan for Rel-17 NR QoE in RAN2 | China Unicom, Ericsson |
| 8.14.2.1 | Configuration architecture general aspects | |
| R2-2102958 | QoE measurement configuration and reporting | Intel Corporation |
| R2-2102963 | QoE configuraiton and reporting general aspects | Qualcomm Incorporated |
| R2-2103049 | Configuration and reporting of QoE measurements | Ericsson |
| R2-2103147 | Discussion on QoE measurement collection in NR | OPPO |
| R2-2103377 | QoE measurement configuration and reporting | vivo |
| R2-2103425 | QoE measurements in NR | LG Electronics Inc. |
| R2-2103555 | Considerations on QoE scope | Nokia, Nokia Shanghai Bell |
| R2-2103556 | QoE reporting control by RAN awareness on QoE parameter | Nokia, Nokia Shanghai Bell |
| R2-2103692 | Configuration and reporting for NR QoE measurement | CMCC |
| R2-2103835 | Discussions on the QoE SI Metrics and Collection Procedures | Apple |
| R2-2103910 | Discussion on QoE measurement configuration and reporting | Huawei, HiSilicon |
| R2-2103934 | General framework for QoE measurements | Samsung Telecommunications |
| R2-2104034 | Discussion on NR QoE configuration | CATT |
| R2-2104082 | Issues for NR QoE measurement | Samsung |
| R2-2104270 | Discussion on NR QoE Configuration | ZTE Corporation, Sanechips |
| 8.14.2.2 | Start and Stop | |
| R2-2102967 | Stop and start of QoE measurement reporting | Qualcomm Incorporated |
| R2-2103050 | Pause and resume of QoE measurements | Ericsson |
| R2-2103146 | Discussion on QoE measurement pausing and resuming | OPPO |
| R2-2103290 | LS reply on QoE Measurement Collection | Qualcomm Incorporated |
| R2-2103378 | QoE measurement handling | vivo |
| R2-2103693 | Start and stop for NR QoE measurement | CMCC |
| R2-2103911 | QoE measurement handling at RAN overload | Huawei, HiSilicon |
| R2-2104035 | Discussion on QoE collection start and stop | CATT |
| R2-2104271 | Discussion on pause/resume NR QoE reporting | ZTE Corporation, Sanechips |
| R2-2104627 | Report of offline discussion: [AT113bis-e][037][eQoE] Pause Resume | Huawei, HiSilicon |
| R2-2104628 | [DRAFT] LS on QoE handling during RAN | Huawei |
| 8.15.1 | Organizational | |
| R2-2102660 | Reply LS on geo-area confinement (S2-2101319; contact: LGE) | SA2 |
| 8.15.2 | SL DRX | |
| R2-2102688 | DRX Design for Sidelink Unicast | CATT |
| R2-2102689 | Further Study on DRX for Sidelink Groupcast/Broadcast | CATT |
| R2-2102690 | DRX Active Time Alignment between Uu and SL | CATT |
| R2-2102771 | Further discussion on Sidelink DRX | LG Electronics France |
| R2-2102801 | Summary of [POST113-e][703][V2X/SL] Details of Timer (InterDigital) | InterDigital |
| R2-2102802 | Further details on SL DRX Timers | InterDigital |
| R2-2102803 | On TX Centric vs RX Centric DRX Configuration Determination | InterDigital |
| R2-2102815 | SL DRX Configuration Impact on RAN1 and RAN2 | vivo |
| R2-2102816 | SL DRX for Unicast | vivo |
| R2-2102817 | SL DRX for Groupcast and Broadcast | vivo |
| R2-2102848 | Discussion on SL DRX impact on SL resource allocation mode 1 | Sharp |
| R2-2102886 | Discussion on DRX configuration | OPPO |
| R2-2102887 | Discussion on network involvement for SL related DRX | OPPO |
| R2-2102888 | Left issues on DRX mechanisms and granularity | OPPO |
| R2-2102889 | Summary of [POST113-e][704] TX UE centric or RX UE centric DRX configuration determination (OPPO) | OPPO |
| R2-2102971 | Discussion on sidelink DRX timer handling | Xiaomi communications |
| R2-2102972 | DRX coordination between Uu and Sidelink | Xiaomi communications |
| R2-2102973 | DRX coordination between TX and RX UE | Xiaomi communications |
| R2-2102979 | Discussion on Coordination between Uu DRX and SL DRX | ZTE Corporation, Sanechips |
| R2-2102980 | Discussion on sidelink DRX configuration for unicast | ZTE Corporation, Sanechips |
| R2-2102981 | Discussion on sidelink DRX configuration for groupcast and broadcast | ZTE Corporation, Sanechips |
| R2-2103003 | General aspects of SL DRX | Ericsson,Qualcomm Incorporated |
| R2-2103004 | Alignment between SL DRX and Uu DRX | Ericsson,Qualcomm Incorporated |
| R2-2103005 | Interaction between partial sensing and DRX | Ericsson |
| R2-2103011 | NR SL DRX | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103068 | On general SL DRX design | Intel Corporation |
| R2-2103069 | Discussion on SL DRX timers | Intel Corporation |
| R2-2103070 | On DRX wake-up time alignment | Intel Corporation |
| R2-2103174 | Consideration on sidelink DRX for broadcast and groupcast | Huawei, HiSilicon |
| R2-2103234 | Discussion on HARQ RTT and Retransmission Timers for SL Unicast | Spreadtrum Communications |
| R2-2103287 | Discussion on HARQ RTT and Retransmission Timer for SL DRX | Fujitsu |
| R2-2103288 | Alignment of sidelink DRX active time | Fujitsu |
| R2-2103305 | On the deciding entity of SL DRX configuration | Nokia, Nokia Shanghai Bell |
| R2-2103306 | Backward Compatibility Issue of SL DRX with Rel.16 Sidelink | Nokia, Nokia Shanghai Bell |
| R2-2103401 | SL DRX configuration for unicast | Lenovo, Motorola Mobility |
| R2-2103462 | Discussion on SL DRX active time for groupcast and broadcast | ASUSTeK |
| R2-2103463 | Discussion on MAC impact regarding Sidelink DRX | ASUSTeK |
| R2-2103468 | Geolocation for Sidelink DRX | Nokia, Nokia Shanghai Bell, Fujitsu, Fraunhofer IIS, Fraunhofer HHI |
| R2-2103470 | Coordination between Uu DRX and SL DRX | Lenovo, Motorola Mobility |
| R2-2103478 | SL DRX Timers | Nokia, Nokia Shanghai Bell |
| R2-2103576 | On detailed SL DRX model | MediaTek Inc. |
| R2-2103577 | On coordination between Uu DRX and SL DRX | MediaTek Inc. |
| R2-2103615 | Discussion on Sidelink DRX | Sony Europe B.V. |
| R2-2103741 | DRX Configuration for Broadcast and Groupcast SL communication | Lenovo, Motorola Mobility |
| R2-2103778 | Discussion on Directional SL DRX for Unicast | Qualcomm Finland RFFE Oy |
| R2-2103779 | Discussion on SL DRX configuration for Groupcast & Broadcast | Qualcomm Finland RFFE Oy |
| R2-2103780 | Discussion on SL DRX Timers and Others | Qualcomm Finland RFFE Oy |
| R2-2103852 | Discussion on remaining issues on SL DRX | Apple |
| R2-2103853 | Discussion on RX-centric and Tx-centric in SL unicast DRX | Apple, InterDigital Inc. |
| R2-2103889 | Coordination between DL DRX and SL DRX | Samsung |
| R2-2103891 | SL DRX operation for groupcast/broadcast | Samsung |
| R2-2103892 | Transmission UE behaviours for SL DRX | Samsung |
| R2-2103894 | Rel-16 SCI information related to active time in SL DRX | Samsung |
| R2-2103952 | SL DRX Granularity Considerations | Convida Wireless |
| R2-2104083 | Remaining issues in which UE decides sidelink DRX configurations | LGE, InterDigital, Huawei, ASUSTeK, Apple |
| R2-2104113 | Discussion on SL communication impact on Uu DRX | Huawei, HiSilicon |
| R2-2104114 | Consideration on the sidelink DRX for unicast | Huawei, HiSilicon |
| R2-2104256 | Consideration on sidelink DRX determination | LG Electronics Inc. |
| R2-2104266 | SL DRX enabled UE Mode 2 operation | ITL |
| R2-2104285 | Discussion on SL DRX configuration for Groupcast & Broadcast | Qualcomm Finland RFFE Oy, Ericsson |
| R2-2104472 | Summary of [706] | Ericsson |
| R2-2104473 | [AT113bis-e][707][V2X/SL] Uu DRX impact to support SL | CATT |
| R2-2104474 | [AT113bis-e][708][V2X/SL] DRX configuration for SL groupcast and broadcast | ZTE |
| 8.15.3 | Resource allocation enhancements RAN2 scope | |
| R2-2102691 | Consideration on Resource Allocation Enhancements | CATT |
| R2-2102746 | Discussion on inter-UE coordination | OPPO |
| R2-2102772 | Power efficient resource allocation | LG Electronics France |
| R2-2102804 | Resource Allocation for eSL | InterDigital |
| R2-2102818 | Discussion on inter-UE coordination for sidelink mode2 | vivo |
| R2-2102970 | Resource allocation enhancement impact in RAN2 | Xiaomi communications |
| R2-2102982 | Discussion on inter-UE coordination | ZTE Corporation, Sanechips |
| R2-2103040 | Power Reduction for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103041 | Inter-UE Coordination for Sidelink Mode 2 Resource Allocation | Fraunhofer IIS, Fraunhofer HHI |
| R2-2103173 | On resource allocation enhancement in Rel-17 NR eSL | Huawei, HiSilicon |
| R2-2103238 | Discussion on resource allocation enhancement for NR sidelink | Spreadtrum Communications |
| R2-2103289 | Dual-mode Configuration and Selection for NR Sidelink | Fujitsu |
| R2-2103400 | Discussion on sidelink resource allocation enhancements | Lenovo, Motorola Mobility |
| R2-2103578 | Transmission of assistance information for Mode 2 enhancement | MediaTek Inc. |
| R2-2103617 | Discusison on Sidelink sensing | Sony Europe B.V. |
| R2-2103664 | General principles for resource allocation enhancements for SL mode 2 | Ericsson |
| R2-2103736 | Resource Allocation Enhancements | Intel Corporation |
| R2-2103854 | Discussion on Inter-UE Coordination | Apple |
| R2-2103855 | Discussion on resource allocation for Pedestrian UE | Apple |
| R2-2103948 | On Resource Allocation Mode 2 Enhancement for NR Sidelink | Convida Wireless |
| R2-2103988 | Resource allocation enhancements | Samsung |
| R2-2104085 | Inter-UE coordination for NR V2X | LG Electronics Inc. |
| 8.15.4 | Other | |
| R2-2102805 | Discussion on Uu DRX for SL UE | InterDigital |
| R2-2103579 | On SL sync search optimization | MediaTek Inc. |
| 8.16.1 | Organizational | |
| R2-2102657 | LS on support of PWS over SNPN (S1-210368; contact: Qualcomm) | SA1 |
| R2-2102658 | Reply LS on clarification request for eNPN features (S2-2101076; contact: Nokia) | SA2 |
| R2-2103592 | RAN2 Work Plan for Enhancement for Private Network Support for NG-RAN | Nokia, China Telecom (Rapporteurs) |
| R2-2103595 | Stage 2 specification for NPN enhancements | Nokia (Rapporteur) |
| R2-2103671 | Proposed reply for LS on support of PWS over SNPN (S1-210368/R2-2102657) | Nokia, Nokia Shanghai Bell |
| R2-2103953 | Discussion on Reply LS on support of PWS over SNPN | Qualcomm Incorporated |
| R2-2104514 | [Draft] Reply LS on support of PWS over SNPN | Qualcomm |
| R2-2104624 | Reply LS on support of PWS over SNPN (S2-2102963; contact: Qualcomm) | SA2 |
| R2-2104640 | Reply LS on support of PWS over SNPN | RAN2 |
| 8.16.2 | Support SNPN with subscription or credentials by a separate entity | |
| R2-2102795 | Support SNPN with subscription or credentials by a separate entity | OPPO |
| R2-2102836 | Support SNPN along with subscription / credentials owned by an entity separate from the SNPN | Intel Corporation |
| R2-2102914 | Further Consideration on Subscription or Credentials by a Separate Entity | CATT |
| R2-2102935 | Resolving issues for SNPN with subscription or credentials by a separate entity | LG Electronics France |
| R2-2103123 | Support SNPN with subscription or credentials by a separate entity | vivo |
| R2-2103170 | Accessing to SNPN with credentials owned by a separate entity | Huawei, HiSilicon |
| R2-2103222 | Access to SNPN with credentials from a different entity | Qualcomm Incorporated |
| R2-2103268 | Cell (re)selection for Rel-17 NPN enhancements | Asia Pacific Telecom co. Ltd, FGI |
| R2-2103593 | Discussion on Group IDs from RAN2 perspective | Nokia, Nokia Shanghai Bell |
| R2-2103618 | Cell reselection using credentials from a separate entity | Sony Europe B.V. |
| R2-2103675 | SNPN access using subscription from external Credentials Holder (CH) | Ericsson |
| R2-2103726 | Left Issues and Analysis on LS from SA2 on Supporting SNPN with Credentials by a Separate Entity | CMCC |
| R2-2103782 | RAN2 impact to support SNPN with credentials by a separate entity | MediaTek Inc. |
| R2-2104041 | On Supporting Visited SNPN with Credentials | Samsung |
| R2-2104235 | Consideration on the Separate Entity Supporting | ZTE Corporation, Sanechips |
| R2-2104290 | Summary Document for AI 8.16.2 | CATT |
| 8.16.3 | Support UE onboarding and provisioning for NPN | |
| R2-2102796 | Support UE onboarding and provisioning for NPN | OPPO |
| R2-2102837 | RAN2 impact on support UE onboarding and provisioning for NPN | Intel Corporation |
| R2-2102915 | Further Discussion on UE Onboarding and Provisioning for NPN | CATT |
| R2-2102936 | Resolving issues for UE onboarding and provisioning for NPN | LG Electronics France |
| R2-2103124 | Support UE onboarding and provisioning for NPN | vivo |
| R2-2103171 | UE onboarding and remote provisioning for SNPN | Huawei, HiSilicon |
| R2-2103223 | UE onboarding and provisioning for NPN | Qualcomm Incorporated |
| R2-2103466 | Consideration of SIB design for UE onboarding and provisioning in eNPN | China Telecommunication |
| R2-2103594 | Onboarding related considerations | Nokia, Nokia Shanghai Bell |
| R2-2103619 | UE on-boarding cell reselection | Sony Europe B.V. |
| R2-2103676 | UE onboarding | Ericsson |
| R2-2103690 | Discussion the issues to support UE on-boarding and remote provisioning | CMCC |
| R2-2103844 | On the need for additional on-boarding options in eNPN | Apple |
| R2-2104043 | On Supporting Onboarding SNPN | Samsung |
| R2-2104236 | Consideration on the Onboarding and Provisioning for NPN | ZTE Corporation, Sanechips |
| R2-2104492 | Summary for UE onboarding and provisioning for NPN | Intel |
| 8.17 | NR R17 Other | |
| R2-2102611 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) (R1-2101976; contact: OPPO) | RAN1 |
| R2-2102619 | LS on Introduction of DL 1024QAM for NR (R1-2102088; contact: Ericsson) | RAN1 |
| R2-2102625 | LS on Agreements Pertaining to L1/L2-Centric Inter-Cell Mobility (R1-2102209; contact: Samsung) | RAN1 |
| R2-2102627 | LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility (R1-2102248; contact: Samsung) | RAN1 |
| R2-2102645 | LS on Rel-17 Tx switching enhancements (R4-2103234; contact: China Telecom) | RAN4 |
| R2-2102652 | LS on handover with PSCell (R4-2103674; contact: Apple) | RAN4 |
| R2-2102661 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) (S2-2101438; contact: Qualcomm) | SA2 |
| R2-2102669 | Reply LS on False Base Station Detection (S3-210756; contact: Huawei) | SA3 |
| R2-2102673 | Reply LS on New Standardized 5QIs for 5G-AIS (Advanced Interactive Services) (S4-210283; contact: Qualcomm) | SA4 |
| R2-2102676 | LS on network sharing with multiple SSBs in a carrier (S5-212403; contact: ZTE) | SA5 |
| R2-2102855 | Discussion on L1 L2-Centric Inter-Cell Mobility | vivo |
| R2-2102869 | Introduction of 1024QAM | Intel Corporation |
| R2-2102870 | Discussion on L1/L2-Centric Inter-Cell Mobility | Intel Corporation |
| R2-2103024 | Discussion on frequency range definition for 52.6 to 71 GHz | ZTE Corporation, Sanechips |
| R2-2103032 | Discussion on handover with PSCell | ZTE Corporation, Sanechips |
| R2-2103033 | CR on RRC processing delay | ZTE Corporation, Sanechips |
| R2-2103034 | CR on RRC processing delay | ZTE Corporation, Sanechips |
| R2-2103079 | Discussion on L1/L2 Mobility | Qualcomm Incorporated |
| R2-2103221 | Reply LS on network sharing with multiple SSBs in a carrier | Nokia Japan |
| R2-2103260 | RAN2 Impacts of L1L2-Centric Inter-Cell Mobility | MediaTek Inc. |
| R2-2103322 | On frequency range definition for 52.6 – 71 GHz | Nokia, Nokia Shanghai Bell |
| R2-2103330 | Considerations on L1/L2 centric inter-cell mobility | Samsung |
| R2-2103340 | Response LS to RAN4 on HO with PSCell requirements | Nokia, Nokia Shanghai Bell |
| R2-2103341 | DRAFT LS Reply on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Samsung |
| R2-2103639 | Discussion on RAN1 LS for L1/L2-Centric Inter-Cell Mobility | Nokia, Nokia Shanghai Bell |
| R2-2103665 | Introduction of DL 1024 QAM for NR | Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2103666 | [Draft] Reply LS on Introduction of DL 1024QAM for NR | Ericsson |
| R2-2103673 | Draft Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility | Nokia, Nokia Shanghai Bell |
| R2-2103823 | On RAN1 LS (R2-21xxxxx) for L1/L2 centric inter-cell mobility | Ericsson |
| R2-2103828 | Frequency range extension for 52-71 GHz | Ericsson |
| R2-2103862 | Clarification on handover with PSCell | Apple |
| R2-2103863 | Draft LS Reply to RAN4 on handover with PSCell | Apple |
| R2-2103864 | RAN impact on the false based station detection | Apple |
| R2-2103866 | L1/L2-centric inter-cell mobility | Apple |
| R2-2104061 | Consideration on network sharing with multiple SSBs in a carrier | ZTE corporation, Sanechips |
| R2-2104062 | Draft reply LS on network sharing with multiple SSBs in a carrier | ZTE corporation, Sanechips |
| R2-2104067 | Consideration on the RAN2 impacts of introducing DL 1024QAM for NR | ZTE corporation, Sanechips |
| R2-2104068 | Introduction of DL 1024QAM for NR FR1 - 38.331 | ZTE corporation, Sanechips |
| R2-2104069 | Introduction of DL 1024QAM for NR FR1 - 38.306 | ZTE corporation, Sanechips |
| R2-2104102 | Draft reply LS on network sharing with multiple SSBs in a carrier | Huawei, HiSilicon |
| R2-2104115 | Support of 1024QAM for NR in TS 38.331 | Huawei, HiSilicon |
| R2-2104116 | RAN2 impact of L1/L2 centric mobility and inter-cell multi-TRP | Huawei, HiSilicon |
| R2-2104133 | Discussion on RAN4 LS on handover with PSCell | Huawei, HiSilicon |
| R2-2104134 | Discussion on SA3 LS on false base statation detection | Huawei, HiSilicon |
| R2-2104135 | Draft reply LS to SA3 on FBS detection | Huawei, HiSilicon |
| R2-2104136 | RAN2 impact to support R17 UL Tx switching enhancement | Huawei, HiSilicon, China Telecom, CATT |
| R2-2104137 | Draft CR to TS38.331 to support Tx switching enhancements | Huawei, HiSilicon, China Telecom, CATT |
| R2-2104138 | Draft CR to TS38.306 to support Tx switching enhancements | Huawei, HiSilicon, China Telecom, CATT |
| R2-2104155 | Discussion of LS on Handover with PSCell from RAN4 | CATT |
| R2-2104156 | Correction on RRC Processing Delay for Handover from NR to E-UTRA | CATT |
| R2-2104249 | Further Clarification on the 35M/45M supporting | ZTE Corporation, Sanechips |
| R2-2104250 | CR on the 35M/45M supporting-R15 | ZTE Corporation, Sanechips |
| R2-2104251 | CR on the 35M/45M supporting-R16 | ZTE Corporation, Sanechips |
| R2-2104530 | Summary of [AT113bis-e][034][1024QAM] | Ericsson |
| R2-2104531 | Introduction of DL 1024 QAM for NR | Ericsson, Nokia, Nokia Shanghai Bell |
| R2-2104532 | [Draft] Reply LS on Introduction of DL 1024QAM for NR | Ericsson |
| R2-2104548 | CR on the 35M/45M supporting-R15 | ZTE Corporation, Sanechips |
| R2-2104549 | CR on the 35M/45M supporting-R16 | ZTE Corporation, Sanechips |
| R2-2104580 | Reply LS to RAN4 on handover with PSCell | RAN2 |
| R2-2104581 | CR on RRC processing delay | ZTE Corporation, Sanechips |
| R2-2104582 | CR on RRC processing delay | ZTE Corporation, Sanechips |
| R2-2104583 | CR on RRC processing delay | ZTE Corporation, Sanechips |
| R2-2104584 | CR on RRC processing delay | ZTE Corporation, Sanechips |
| R2-2104606 | Reply LS on network sharing with multiple SSBs in a carrier | RAN2 |
| R2-2104626 | Reply LS to SA3 on FBS detection | RAN2 |
| R2-2104632 | Summary of email discussion [AT113bis-e][035][feMIMO] L1L2 Centric Mobility (Samsung) | Samsung |
| R2-2104638 | Summary of [AT113bis-e][026][NR17] SA related (Huawei). | Huawei |
| R2-2104645 | Reply LS on Introduction of DL 1024QAM for NR | RAN2 |
| 9.1.1 | Organizational | |
| R2-2104042 | Work plan of Rel-17 enhancements for NB-IoT and LTE-MTC | Ericsson, Huawei |
| R2-2104451 | RAN2 agreements for Rel-17 NB-IoT and LTE-MTC | Document Rapporteur (Ericsson) |
| 9.1.2 | NB-IoT neighbor cell measurements and corresponding measurement triggering before RLF | |
| R2-2103014 | Condition for NB-IoT connected mode neighbour cell measurement | Qualcomm Incorporated |
| R2-2103191 | Signalling procedure for connected mode measurements support for reestablishment time reduction | Nokia, Nokia Shanghai Bells |
| R2-2103241 | Further discussion on the corresponding measurement before RLF | Spreadtrum Communications |
| R2-2103320 | RAN2 aspects of measurement in connected mode | ZTE Corporation, Sanechips |
| R2-2103394 | Neighbor cell measurements triggering before RLF | Lenovo, Motorola Mobility |
| R2-2103486 | Neighbour cell measurements in RRC_CONNECTED | Huawei, HiSilicon |
| R2-2103925 | Discussion on Fast RLF Recovery procedures in NB-IoT | Ericsson |
| R2-2104653 | Reply LS on neighbour cell measurement in NB-IoT RRC_CONNECTED state (R4-2105800; contact: Huawei | RAN4 |
| 9.1.3 | NB-IoT carrier selection based on the coverage level, and associated carrier specific configuration | |
| R2-2103015 | Determining paging carrier suitability | Qualcomm Incorporated |
| R2-2103176 | Carrier selection enhancement | MediaTek Inc. |
| R2-2103192 | Further analysis on paging carrier selection options | Nokia, Nokia Shanghai Bells |
| R2-2103242 | Further discussion on enhanced paging carrier selection and NPRACH carrier selection | Spreadtrum Communications |
| R2-2103321 | Details of CEL-based paging carrier selection | ZTE Corporation, Sanechips |
| R2-2103487 | Summary of [Post113-e][351][NBIOT R17] Paging carrier selection | Huawei |
| R2-2103927 | Comparing solution for NB-IoT paging carrier selection | Ericsson |
| R2-2104450 | Report of [AT113bis-e][301][NBIOT/eMTC R17] NB-IoT Carrier Selection (Qualcomm) | Qualcomm Incorporated |
| 9.1.4 | Other | |
| R2-2103364 | Consideration on supporting 14 HARQ for eMTC | ZTE Corporation, Sanechips |
| R2-2103365 | Consideration on supporting 16QAM for NB-IoT | ZTE Corporation, Sanechips |
| R2-2103488 | Discussion on 16-QAM for NB-IoT | Huawei, HiSilicon |
| R2-2103489 | Support of 14 HARQ Processes in DL, for HD-FDD Cat M1 UEs | Huawei, HiSilicon |
| R2-2103490 | Support of DL TBS of 1736 bits for HD-FDD Cat. M1 UEs | Huawei, HiSilicon |
| R2-2103926 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| 9.2.1 | Organizational scenarios and scope | |
| R2-2102663 | Reply LS on IoT-NTN basic architecture (S2-2101663; contact: MediaTek) | SA2 |
| R2-2102743 | Discussion on scope of IoT over NTN | OPPO |
| R2-2102828 | Identifying Essential Topics in IoT-NTN | MediaTek Inc. |
| R2-2102956 | Determination of essential parts for IoT NTN | CATT |
| R2-2102961 | Essential adaptations for discontinuous coverage in IoT-NTN | Gatehouse Satcom A/S, Sateliot |
| R2-2103177 | Essential functionality for IOT NTN | Beijing Xiaomi Mobile Software |
| R2-2103189 | Analysis on essential parts for IoT-NTN functionality for Rel-17 | Nokia, Nokia Shanghai Bells |
| R2-2103509 | Discussion on essential functionalities for IOT NTN | Huawei, HiSilicon |
| R2-2103800 | FS_LTE_NBIOT_eMTC_NTN work plan | Eutelsat S.A., MediaTek |
| R2-2104016 | Discussion on essential functionality in IoT NTN - scenarios and scope | Ericsson |
| R2-2104552 | [Offline-027] IOT NTN essential parts (Huawei) | Huawei |
| R2-2104648 | TP for TR 36.763 capturing RAN2 #113bis-e agreements | Eutelsat S.A., MediaTek |
| 9.2.2 | User Plane | |
| R2-2103843 | On Preamble Ambiguity in Non Terrestrial Networks | Apple |
| 9.2.3 | Mobility and Tracking Area | |
| R2-2102744 | Discussion on control plane for IoT over NTN | OPPO |
| R2-2102829 | On Cell-Reselection in NR-NTN | MediaTek Inc. |
| R2-2102957 | Discussion on the mobility of IoT over NTN | CATT |
| R2-2103051 | Connected mode and idle mode mobility | Qualcomm Incorporated |
| R2-2103136 | Discussion on RRC Idle mobility for IoT NTN | Xiaomi |
| R2-2103183 | Discussion on connected mode mobility in NB-IoT and eMTC NTN | Xiaomi Communications |
| R2-2103190 | On the mobility aspects of IoT-NTN | Nokia, Nokia Shanghai Bells |
| R2-2103243 | Discussion on the issue of mobility for IoT over NTN | Spreadtrum Communications |
| R2-2103342 | Control plane aspects of IoT over NTN | ZTE Corporation, Sanechips |
| R2-2103411 | Potential issues in IoT NTN with discontinuous coverage | Lenovo, Motorola Mobility |
| R2-2103412 | Further considerations on RLF-based mobility for NB-IoT in NTN | Lenovo, Motorola Mobility |
| R2-2103510 | Discussion on Mobility for NTN NB-IoT | Huawei, HiSilicon |
| R2-2103511 | Discussion on discontinuous coverage for NTN NB-IoT | Huawei, HiSilicon |
| R2-2103727 | RLF-based NB-IoT mobility in NTN | CMCC |
| R2-2103730 | Discussion on TA Update for IoT-NTN | CMCC |
| R2-2104017 | Mobility for NB-IoT and LTE-M in NTN | Ericsson |
| R2-2104298 | Discussion on TA Update for IoT-NTN | CMCC |
| R2-2104551 | Summary for Control Plane Procedures in IoT-NTN | MediaTek Inc. |
| 9.2.4 | Other | |
| R2-2102745 | Discussion on system information enhancement for IoT over NTN | OPPO |
| R2-2102830 | On Providing Ephemeris Information in IoT-NTN | MediaTek Inc. |
| R2-2103052 | Enhancement to SIB acquisition | Qualcomm Incorporated |
| R2-2103233 | On system information enhancement and IoT features applicability for NTN | Nokia, Nokia Shanghai Bell |
| R2-2103357 | SIB and IoT features applicability for IoT over NTN | ZTE Corporation, Sanechips |
| R2-2104020 | Connection density evaluation for IoT NTN devices | Ericsson |
| R2-2104033 | Summary of [Post113-e][055][IoT NTN] Performance evaluation | Ericsson |
| 9.3 | EUTRA R17 Other | |
| R2-2102605 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (C1-211461; contact: Qualcomm) | CT1 |
| R2-2102607 | User location identification from Carrier Aggregation secondary cell activation messages (FSAG Doc 88_009; contact: GSMA) | GSMA |
| R2-2102659 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC (S2-2101306; contact: Qualcomm) | SA2 |
| R2-2102667 | LS on User Plane Integrity Protection for eUTRA connected to EPC (S3-210563; contact: Vodafone) | SA3 |
| R2-2102703 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation |
| R2-2102721 | Introduction of event-based trigger for LTE MDT logging | KDDI Corporation |
| R2-2102819 | UE location attack based on SCell activation | Ericsson |
| R2-2103016 | User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R2-2103295 | User Plane Integrity Protection for LTE | Samsung |
| R2-2103865 | RAN impact on UP IP for eUTRA connected to EPC | Apple |
| R2-2103928 | Discussion on Capturing PDCP Impacts for User Plane Integrity Protection | Ericsson |
| R2-2103962 | PDCP for Integrity protection for LTE EPC | Intel Corporation |
| R2-2104039 | Discussion on user location identification from SCell Activation | Huawei, HiSilicon |
| R2-2104325 | Summary of [AT113bis-e][202][LTE] UPIP for LTE Rel-17 (Qualcomm) | Qualcomm |
| R2-2104335 | Draft Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | Qualcomm Incorporated |
| R2-2104349 | Reply LS on User Plane Integrity Protection for eUTRA connected to EPC | RAN2 |
| 10.1 | Session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing | |
| R2-2104301 | Report from session on LTE legacy, Mobility, DCCA, Multi-SIM and RAN slicing | Vice Chairman (Nokia) |
| 10.2 | Session on R16 eMIMO, CLI, PRN, RACS and R17 NTN and RedCap | |
| R2-2104302 | Report from Break-Out Session on R17 NTN and RedCap | Vice Chairman (ZTE) |
| 10.3 | Session on eMTC | |
| R2-2104303 | Report eMTC breakout session | Session chair (Ericsson) |
| 10.4 | Session on NR-U, Power Savings, NTN and 2-step RACH | |
| R2-2104304 | Report for Rel-17 Small data and URLLC/IIoT | Session chair (InterDigital) |
| 10.5 | Session on positioning and sidelink relay | |
| R2-2104305 | Report from session on positioning and sidelink relay | Session chair (MediaTek) |
| 10.6 | Session on SON/MDT | |
| R2-2104306 | Report from SOM/MDT session | Session chair (CMCC) |
| 10.7 | Session on NB-IoT | |
| R2-2104307 | Report NB-IoT breakout session | Session chair (Huawei) |
| 10.8 | Session on LTE V2X and NR V2X | |
| R2-2104308 | Report from session on LTE V2X and NR SL | Session chair (Samsung) |